Debug a workflow run
On this page
Start from a specific failing request and follow its recorded execution path. This is more reliable than editing several nodes based on the final error alone.
Locate the run#
Open Workflows → API Action Logs, choose the environment and a narrow time range, and find the request by action, status, or available identifiers. Open its workflow/session detail.
Record the method, route, input shape, version, status, and first failed node. A later node may be absent because execution stopped earlier; that is different from a broken connection.
Inspect the first divergence#
Compare the expected path with the recorded nodes. Check:
- Did authentication succeed before business logic?
- Was the required selector available on this branch?
- Did the Function receive the expected JSON shape?
- Did the HTTP Request call the correct upstream and environment?
- Did the Database node use the intended binding?
- Did a Condition return false legitimately?
A false condition is not automatically an error. Inspect the input and intended rule before changing it.
Reproduce safely#
Create a sandbox request with fixture data and fresh credentials. Stored logs may have erased sensitive values, so replaying a captured request can require replacement credentials.
Use the editor's available debug and step controls to inspect intermediate state. Displayed debug values can be redacted while execution still has the private values it needs.
Use session diagnosis#
Where available, Diagnose session creates a read-only analysis of recorded execution evidence. It can help identify likely failure points but cannot recover data that was never logged or prove an upstream operation succeeded. Review the evidence and limitations in the report.
Verify one fix at a time#
Change the smallest relevant part of the draft, rerun the failing case, and test the neighboring success/denial paths. If the edit introduces a regression, recover a known version before making further speculative changes.
See logs and retention and Maintenance.
Need to investigate a problem? Start with troubleshooting
