Troubleshooting Center¶
Audience: Everyone · Tags:
troubleshooting,support
Something not working? Start here. Every failed run already tells you the cause and a suggested fix — open the run in the Flow Debugger before doing anything else.
Pick your symptom¶
| Symptom | Article |
|---|---|
| Can't sign up or log in | Authentication errors |
| My flow's webhook never triggers it at all | Flow not running |
| I'm not sure my webhook actually fired / need to rotate a leaked URL | Webhook issues |
| A flow runs but an action step fails | Connector failed |
A run is stuck in queued/running, or ended in retry_exhausted |
Execution failures |
| "not found" where I expected access, or I can't add a member | Missing permissions |
429 / RATE_LIMITED on a webhook call |
Rate limiting |
| Snap Studio asked me a question, or a check/test run didn't go the way I expected | Snap Studio problems |
How to read a failure in 60 seconds¶
- Open the run. Flows → the flow → the run, or Dashboard → Recent Runs.
- Read the status.
succeeded,failed,cancelled,retry_exhausted, or still moving (queued,running,retry_pending,retry_running). - Read the error code on the failing step. It tells you the category of problem — see the table below.
- Apply the suggested fix shown on the run (
problem.suggestionin Snap Studio, or the debugger's suggested fix), or jump to the matching article above.
Failure taxonomy¶
Every failed step carries one of these error codes:
| Code | What it means | Fix |
|---|---|---|
auth |
A credential is missing, expired, or invalid. | Reconnect the app (Marketplace → the connector → reinstall/reconfigure); for Email, check the operator's SMTP_* settings. |
rate_limit |
The destination app throttled the request. | Slow down, or add a retry policy. |
timeout |
The destination was too slow to respond. | Retry; check the destination's status. |
upstream_5xx |
The destination returned a server error. | Retry later; check the destination's status page. |
bad_request |
The action's inputs were wrong or incomplete. | Check the flow's field values. |
blocked |
A URL was blocked by SSRF protection. | Use a public https address, not a private/internal one. |
unknown |
Something unexpected happened. | Open the run in the debugger; if it repeats, contact support with the run ID. |
Full detail and connector-specific notes: Connector failed.
When to contact support¶
Reach out if a failure has error code unknown and repeats, a run is stuck
for an unusually long time, results don't match what the connected app
shows, or you've followed the matching article and it's still failing.
Include: - The run ID (visible on the run, and in its URL). - The flow name. - When it happened. - What you expected to happen instead.
We can look up a run by its ID alone — we never need your passwords or connector credentials.
Related: Flow Debugging · Monitoring Runs · Glossary
Was this helpful? 👍 👎