Troubleshoot Workflow Runs
Fix workflow validation, trigger, action, and run failures.
Workflow issues usually come from missing configuration, disconnected integrations, invalid record data, permissions, or a workflow graph that does not connect correctly.
Start with the latest run detail when a workflow ran. Start with publish and trigger checks when no run was created.
Workflow Will Not Publish
Check for these problems:
- Missing trigger.
- More than one trigger.
- Required trigger or action fields are empty.
- Edges point to deleted nodes.
- A condition branch is not connected.
Workflow Did Not Run
Confirm the workflow is published, the trigger event actually happened, and the module or integration involved is enabled.
Also check whether the trigger conditions were too narrow, the workflow was paused or unpublished at the time, or the event happened in a different workspace or module.
If the workflow depends on imported or synced data, confirm whether those events are allowed to trigger it. Some workflows should run only for human-created records, while others must handle imports intentionally.
Start With One Record
Pick one record that should have triggered the workflow. Check its timeline, status, field values, owner, workspace, and creation/update time. Then compare those facts with the trigger conditions.
This is faster than changing the workflow broadly without knowing which condition failed.
Action Failed
Open the run detail and read the failed step. Check whether the action depends on a missing field, deleted record, disconnected app, expired credential, or permission that changed.
Fix the first failed step before rerunning. Later failures may only be side effects of the earlier missing value or skipped action.
Use the run detail input and output panels to compare what the workflow received with what the action expected. Missing fields are often caused by a trigger or condition earlier in the graph, not by the failed action itself.
Too Many Actions Ran
Review For Each steps, trigger frequency, and schedule settings. Test with a small record set before using broad automation.
If duplicate records were created, pause the workflow before cleanup. Then review trigger frequency, idempotency fields, and whether the same record can match more than one branch.
Safe Retry
Before rerunning, check what the failed run already completed. Do not rerun a workflow that sends emails, creates invoices, posts messages, or updates records until duplicate effects are understood.
Use the run detail as the retry checklist. Mark which steps already created records, sent messages, or called providers before deciding whether to rerun or clean up manually.
Cleanup After Failures
If a failed run already created records, sent messages, or updated fields, clean or document those effects before retrying. Otherwise the retry may appear successful while leaving duplicate work behind.
Recovery Checklist
Before turning the workflow back on:
- pause it if duplicate actions are possible
- fix the first failed step
- test with one safe record
- confirm connected apps and permissions
- review whether completed actions need cleanup
- document the cause if the workflow is business-critical
After recovery, monitor the next few live runs. A workflow can pass one manual test and still fail on older records, imported records, or records with missing optional fields.
Evidence To Collect
For support or admin review, collect the workflow name, run URL, trigger record, failed step, error text, connected app status, and any customer-facing effects. This keeps troubleshooting focused on the actual failing path.