Zap turned off, held or not triggering: how to get it running again

You see: Zap turned off · run on hold · Zap not triggering

What it means

A Zap that errors again and again is turned off automatically. Runs are held when flood protection kicks in, an app is disconnected, the account hit its task limit, or there is a payment problem. A trigger that never fires is usually a disconnected account or a required trigger field left empty.

How to fix it

Open Zap history and filter by status: errored runs explain why the Zap was turned off, held runs say why they were held.
Fix the cause it names: reconnect the app, raise or wait out the task limit, or update the payment details.
Replay the held runs, then turn the Zap back on.
If the trigger never fires, check that its account is still connected and its required fields are filled, then create a new item in the app and test the trigger again.

If it keeps coming back

Runs marked safely halted or handled error do not turn a Zap off; only repeated errors do. Fix the step that errors and the Zap stays on.

Still stuck? Ask Void, free

Paste the error and what the automation does. Void names the likely cause and the fix, in seconds, no account.

Ask Void about this error

Or have it fixed: $25

One broken automation, diagnosed and repaired, with proof it runs again. Reply to the receipt with what stopped.

Get the One-Time Fix

The One-Time Fix covers one workflow. What you send and what you get back.