Short answer
Why Is My Zap Stuck in a Loop?
A Zap loops when its action changes the same record watched by its trigger, or when two workflows update each other without an exclusion rule. Trace the record ID across Zap History, identify the write that creates the next trigger event, then add a processed marker or a trigger condition that excludes automation-made updates.
Common causes
- The Zap updates the same object monitored by its updated-record trigger.
- Two Zaps write changes that trigger one another.
- A webhook is echoed back to the sending workflow.
- The workflow lacks a processed flag, origin value, or stable deduplication key.
Diagnostic steps
- Pause every workflow that can write the affected record to stop new runs safely.
- Follow one record ID through its repeated runs and locate the action immediately before each retrigger.
- Add an origin or processed field and exclude that value at the trigger or first filter.
- Turn on one workflow at a time and test with a new record while monitoring history.
Example
A Zap triggered by any Airtable record update writes “Synced” to that record. The write triggers another run. Limit the trigger to a view that excludes Synced records.
Caveats
Pausing only one workflow may not stop a multi-workflow cycle. Avoid deleting evidence until the trigger chain is understood.