Workflows
Workflow failures and debugging
Trace trigger matching, validation, branch decisions, node failures, variables, integrations, and usage.
Automation buildersAdministratorsIntermediateAvailable
What this guide covers
- Workflow debugging starts with status and trigger evidence, then narrows to the first failing or unexpected node.
- Prerequisites: The workflow ID, approximate time, trigger context, and any execution or message identifier.
- Result: The same input follows the expected path and live monitoring no longer shows the failure.
- Limit: The current no-code UI does not expose a single downloadable execution log bundle or rollback history.
What this is and when to use it
Workflow debugging starts with status and trigger evidence, then narrows to the first failing or unexpected node.
| Use it when | Expected outcome |
|---|---|
A workflow did not start. | The same input follows the expected path and live monitoring no longer shows the failure. |
A workflow chose the wrong path. | The same input follows the expected path and live monitoring no longer shows the failure. |
A node failed or returned unexpected data. | The same input follows the expected path and live monitoring no longer shows the failure. |
Before you begin
- The workflow ID, approximate time, trigger context, and any execution or message identifier.
Prerequisites
The workflow ID, approximate time, trigger context, and any execution or message identifier.
Complete the task
- Confirm the workflow is Active and Saved.
- Check that the event matches the configured number and trigger.
- Reproduce with Test using the same input shape.
- Inspect the first failed node, branch decision, variables, and configuration issues.
- Validate connected accounts, functions, templates, number status, and Balance.
- Correct the cause and test again before reactivation.
Confirm it worked
- The same input follows the expected path and live monitoring no longer shows the failure.
Common problems
| Symptom | What to check |
|---|---|
No execution exists | Investigate workflow status and trigger matching. |
Execution exists but stops | Open the first failed node rather than debugging later nodes that never ran. |
Current limitations
The current no-code UI does not expose a single downloadable execution log bundle or rollback history.
Product boundary
The current no-code UI does not expose a single downloadable execution log bundle or rollback history.
Where to go next
Related documentation
A workflow is not runningCheck Active status, saved validation, trigger matching, selected number, schedule timezone, and webhook input.A workflow node failedInspect the first failed node, exact fields, outputs, branch, connection, resource, and external status.Variables contain unexpected valuesCheck variable scope, exact path, trigger context, execution branch, preceding node output, and value type.