Zapier: Safely halted (Halted)
Last verified
Safely haltedWhat it means
Safely halted is a run status, not an error. Zapier's help center defines it as a run that stopped intentionally, most often because a search step found no results. Older interfaces and many community posts call it simply "Halted". The run details usually show the reason in a yellow box (errors are shown in red).
Zapier states that safely halted runs do not count toward turning your Zap off. Later steps that did not run show as Skipped. However, if a later step has required fields mapped from the halted step, that later step can error.
What is not wrong: Zapier and your connected apps are working. The Zap did what it was configured to do when the data did not match.
What it looks like
Run status: Safely halted
Step 2 (Find Row): Safely halted - no rows found matching the search
Step 3: SkippedWhy it happens
- A search step found no matching record and is set to halt when nothing is found.
- A step returned no data to work with.
- An app's action deliberately stopped the run (for example, a duplicate check).
How to fix it
- Open the run in Zap history and read the yellow halt message.
- If a search halts but you want the Zap to continue, enable the option to continue or create the record if it is not found, where the app offers it.
- Use Paths or a Filter to handle the no-result case explicitly.
- Check that the search value is correct (spacing, case, field format).
How to stop it recurring
Design for the empty case: add a Filter or Path for "record not found", or use search-or-create actions. If halts are expected, they need no action; if they are not, review the search criteria and the trigger data.
Official documentation: help.zapier.com/hc/en-us/articles/20505304170637. See all Zapier error messages or the Zapier limits and quotas.
Related errors
Definitions
Quick answers
What does "Safely halted (Halted)" mean in Zapier?
Safely halted is a run status, not an error. Zapier's help center defines it as a run that stopped intentionally, most often because a search step found no results. Older interfaces and many community posts call it simply "Halted". The run details usually show the reason in a yellow box (errors are shown in red). Zapier states that safely halted runs do not count toward turning your Zap off.
How do I fix "Safely halted (Halted)"?
1. Open the run in Zap history and read the yellow halt message. 2. If a search halts but you want the Zap to continue, enable the option to continue or create the record if it is not found, where the app offers it. 3. Use Paths or a Filter to handle the no-result case explicitly. 4. Check that the search value is correct (spacing, case, field format).
Error handling you can see in the workflow
Autonoly workflows have per-node retries, timeouts, continue-on-fail and error-handler branches, so a failing step can be retried or routed instead of stopping the whole run. Saved workflows have no loop node; lists are worked through by the AI agent or one run per trigger item.
Also see Visual workflow builder.