Troubleshooting & Common Errors
Match the symptom in your run, Step, or connected app to the right troubleshooting guide. This index gives you the first check, then routes you to the focused troubleshooting page.
- Use it to
- Triage a missing run, paused execution, wrong field value, external API failure, or Step validation error
- Find it
- Canvas → Execution Log and Step App drawer → Executions tab
- Instead
- Step Error Messages (when you already have an exact validation message or error code)
Before starting another run
If a run exists, open its Execution Log and find the first unexpected Step. In that Step’s Executions tab, match the timestamp and execution ID, then expand the result or error. If no run appears, start with It did not start or is still waiting below.
Check the destination before retrying a write. A failed run or timeout does not prove that a message, record, or charge was never created. Inspect the connected app first. If the execution is still running, inspect that run rather than start another. For partial or uncertain writes, follow Connections and External APIs.
Symptom index
No run appeared, a webhook seems missing or the run is paused on Wait or Human Review.
It did not start or is still waitingA reference stayed literal, a field is empty, the data has the wrong shape or only one list item was processed.
A value is missing or wrongAn app reports 401, 403, 429 or a timeout, or an external write may have completed only partly.
A connection or API failedLook up validation messages from routing, list-processing, loop and Human Review Steps.
A Step shows an exact errorTrace the first unexpected result through the Execution Log, Step executions and upstream data.
The run failed, but the cause is unclear- Run
- Open the Execution Log for the affected automation and locate the first unexpected Step.
- You should see
- You can classify the symptom into one of the five guides above before retrying.
What’s Next?
- Read what a single run actually did in the Execution Log.
- Choose between saved-data replay, a real action test, and an automation run in Testing & Debugging.
- Design a recovery path with Error Handling & Retries.