Monitoring and troubleshooting advanced action flows (EAP)

Every time anadvanced action flowruns, including tests, the details of that run are recorded in the workflow's execution history. The execution history is the starting point for troubleshooting errors and maintaining your advanced action flows.


What's my plan?







All Suites

Growth, Professional, Enterprise, or Enterprise Plus







Summary: ◀▼
You can monitor advanced action flows by viewing their execution history, which logs details like status, input, output, and errors. Troubleshoot issues by verifying the flow is published, checking triggers, permissions, and reviewing console and network logs. Common errors include HTTP issues, timeouts, and data limits. Debug failed runs by examining error messages, network requests, and input, then test and publish fixes.




Every time an advanced action flow runs, including tests,
the details of that run are recorded in the workflow's execution history. The execution
history is the starting point for troubleshooting errors and maintaining your advanced
action flows.
This article contains the following topics:
Viewing the execution history
Troubleshooting errors in advanced action flows



Related articles
Creating advanced action flows
(EAP)
Editing and managing advanced action
flows




Viewing the execution history

The execution history list provides a summary of each execution, and can be used to
access more information about each execution.
Test runs are clearly labeled so they are easy to differentiate from production
executions.

To view an advanced action flow's execution history
In Admin Center, click
Apps and integrations in the sidebar, then select Actions > Advanced action
flows.
Next to the advanced action flow you want to monitor, click the options menu
( ) and select Execution history. A list
of every execution is displayed including the status, trigger, start
time, duration, version, input, output, and any error that occurred for
each.

(Optional) Search for specific executions based on input, output, or
triggering user values.
To view more details about an execution, click the execution. The detail
view of an execution includes the flowchart view of the workflow and
five tabs of details:

Console: Timestamped log of every event during the
execution.

Input: The input values for the execution.

Output: The output values for the execution.

Code: The version of the advanced action flow's code that
was used for the execution.

Network: A record of all API calls and the HTTP methods
of each.








Troubleshooting errors in advanced action flows

Use the following suggestions to verify an advanced action flow is working and
diagnose common failures:
Verifying an advanced action flow is working
Troubleshooting advanced action flows that don't run
Troubleshooting runtime and data issues
Debugging failed executions




Verifying an advanced action flow is working

If you have created an advanced action flow that doesn't appear to be running, do
the following in order to verify whether it's wokring:

Check whether the advanced action flow is published. An
advanced action flow must be saved, published, and active in order
to run. On the Advanced action flows page in Admin Center, check
that it is labeled as Active. If it is labeled as
Draft or Inactive, use the options menu to publish
or activate it.


Verify that you're expecting the published version of the advanced
action flow. Saving a new or updated advanced action flow
creates a draft. It doesn't publish that version of the workflow. If
the execution history shows an Outdated version tag next to
the latest execution, the running code doesn't reflect your latest
updates. Use the Advanced action flows page in Admin Center to
publish the latest version of the workflow.


Check whether the advanced action flow has ever run. Use the
advanced action flow's execution
history to check whether the workflow has ever run. If
there are no executions in the list, the advanced action flow
trigger isn't firing. See Troubleshooting advanced action flows that don't run.

If the advanced action flow has executed at least once, the
trigger worked and the problem is in the workflow logic. See Troubleshooting runtime and data
issues.


Check whether the advanced action flow trigger's conditions match
your data. A trigger condition that never evalutes to true
prevents every run. Edit the advanced action
flow to make sure any trigger conditions are valid.


Ensure the admin who created the advanced action flow has permission
to access every API and system used in the workflow. Advanced
action flows are run with the permissions and access of the admin
who created it. If the creator can't access parts of the workflow,
run-time failures will occur.


Review the console and network tabs of the advanced action flow's
most recent execution. The console and network tabs in the
detailed view of an execution explain almost every failure that can
occur. Use that information to update the advanced action
flow.






Troubleshooting advanced action flows that don't run

If an advanced action flow isn't running, verify that it's working.
If you've verified it's working but it still isn't running, then use the table to
resolve the symptoms you're experiencing.








Symptom
Solution




Runs for some records, but not others
Likely caused by an overly-narrow trigger condition or an
empty field in the records that it doesn't run
on. Solution: Add a null check, such as
custom_fields.department !=
null



Web trigger returns HTTP 405
The HTTP method doesn't match the configured
method. Solution: Change the call's method
or reconfigure the web trigger.



Web trigger returns HTTP 404
The wrong workflow ID or the workflow isn't published as
a web trigger. Solution: Recopy the
URL from the advanced action flow web trigger
node.









Troubleshooting runtime and data issues

If your advanced action flow is running, but you're experiencing errors, use the
table to resolve the symptoms you're experiencing.








Error or Symptom
Solution




Web trigger returns 200, but nothing happens
It is expected that web triggers respond before they
run. Solution: Check the execution
history. Under load, executions are queued
and there might be delays.



Scheduled flow runs at an unexpected hour
Schedule triggers run in UTC time and don't observe
daylight savings time. Solution: Adjust the
described schedule with an offset for UTC
time.



Scheduled flow ran twice for one interval
Schedule triggers run at least once per
interval. Solution: Make the advanced
action flow idempotent by recording completion in
storage and check that
first.



HTTP 403 or allowlist error from a Zendesk
endpoint
The endpoint is denied or the advanced action flow's
creator doesn't have permission to access
it. Solution: Review the allowlist and
ensure you are using allowed endpoints. If you are,
check the workflow creator's permissions.



HTTP 404 from a Zendesk endpoint
The record doesn't exist or the advanced action flow's
creator doesn't have permission to access
it. Solution: Verify the record's ID and
the workflow creator's permissions to access
it.



JTTP 422 from a Zendesk endpoint
The request body doesn't match the API's
expections. Solution: Review the response
body in the Network tab of the workflow's execution
history.



HTTP 429
You've hit a rate limit. Solution: Add
sleep() between calls in loops, or
narrow the trigger condition to reduce the volume of
calls.



HTTP 401 or 403 from an external system
The connection isn't authorized or is using incorrect or
expired credentials. Solution: Re-authorize the
connection or re-enter the secret. See Connecting advanced
action flows to external systems.



Execution timeout
The workflow ran past the time limit.
Solution: Reduce data processing per
execution. For example, process one page of data per run
and store a cursor, or split it into multiple advanced
action flows.



Advanced action flow sandbox heap limit exceeded
The advanced action flow help too much data in memory at
once. Solution: Split data into streams or
pages rather than accumulating everything in an
array.



storage value exceeds 4096 bytes
The size of the storage value is too
large. Solution: Store an identifier and
re-fetch the data rather than storing the
payload.



storage limit reached: 1000 keys
The scope is full. Solution: Delete storage keys
no longer in use. Storage keys never automatically
expire, so must be removed manually.



agents.run() input too large
The prompt plus inline text exceed 20
KiB. Solution: Move large content into
files or summarize it before
sending.



workflow output exceeds limit
Output exceeded 2 MB. Solution: Return a summary
or identifiers rather than full payloads.



Rows exceeded the parse limit
Over 10,000 rows in one parse. Solution: Split
the data into smaller files or process it in multiple
parts.



AI step returns an empty or incorrect result
An attachment is unsupported or unreadable, or the prompt
is ambiguous. Solution: Use the network tab of the
execution
history to confirm the file downloaded, and
then use output.schema instead of
parsing free text.



Values are missing after a pause
Local variables don't survive a
pause(). Solution: Re-read
the value from input, a platform call,
or storage. See Understanding
advanced action flow states, storage, and
pauses.



Paused flow never resumed
Pause exeeded 30 days, no resume event occurred, or the
event condition never matched. Solution: Check the
pause() configuration. For an
indefinite pause, you can resume from the execution
history.



Something happened twice
The advanced action flow resumed and a side effect wasn't
tracked by the platform. Solution: Use platform
operations for side effects and record completion in
storage before acting.




require is not defined or import fails
Third-party packages aren't available. Solution:
Use the built-in data utilities and
globals.



Maximum number of workflows reached
(100)
The account has the maximum number of advanced action
flows. Solution: Delete an unused advanced
action flow.









Debugging failed executions

If your advanced action flow is working in general but an error occurs causing an
execution to fail, do the following to debug the issue.
You can also revert to an earlier version of the advanced
action flow if necessary.
Tip: It
can be helpful to reproduce the failure in a test run before changing
anything. To do this, copy the failing execution's input and use it as your
test input.


To debug a failed execution
In Admin Center, click
Apps and integrations in the sidebar, then select Actions > Advanced action
flows.
Next to the advanced action flow you want to debug, click the options
menu ( ) and select Execution history.
Click on the failed execution to view the details.
Check whether an Outdated version tag is present on the
execution. If so, the problem may be fixed in a newer
version.

On the Console tab, read the error and stack trace, and note the
last step that was logged as successfully completed.
Click on the Network tab, and click one of the failed requests
highlighted in red to view the request and response headers and
bodies. For HTTP 4XX errors, the response body usually names the
exact problem.

Compare the Input tab against your expected input.
Fix the advanced action flow, either by clicking Try fix to have
the AI attempt a repair or by editing the code directly or using the AI
chat panel.

Test the updated advanced action
flow.
Click Publish.





{
"@context": "https://schema.org",
"@type": "TechArticle",
"@id": "https://support.zendesk.com/hc/en-us/articles/11156051159962-Monitoring-and-troubleshooting-advanced-action-flows-EAP",
"url": "https://support.zendesk.com/hc/en-us/articles/11156051159962-Monitoring-and-troubleshooting-advanced-action-flows-EAP",
"headline": "Monitoring and troubleshooting advanced action flows (EAP)",
"description": "You can monitor and troubleshoot advanced action flows by viewing their execution history and using detailed logs and error information to diagnose and resolve issues.",
"articleSection": "Product help",
"datePublished": "2026-08-21T07:39:51+00:00",
"dateModified": "2026-08-25T14:39:06.749602+00:00",
"inLanguage": "en-US",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://support.zendesk.com/hc/en-us/articles/11156051159962-Monitoring-and-troubleshooting-advanced-action-flows-EAP"