ERR_RECURSION_LIMIT on Zapier: Recursion limit exceeded. Root cause: The workflow has triggered itself recursively too many times, exceeding the platform's maximum recursion depth. This occurs when an automation updates a record that triggers the same automation again, without a proper termination condition to break the cycle. Step 1: Identify the self-triggering path. In Zapier, open the task history for the failing Zap. Look for multiple task entries with the same Zap name firing in rapid succession — this confirms the recursion. Trace what the Zap's final action does: if it updates or creates a record that the Zap's trigger watches, you have found the loop. Step 2: Add a filter step to break the loop. Add a Zapier Filter step immediately after the trigger. Create a condition that detects whether this run was triggered by the Zap itself. A common approach: add a custom field (e.g. "zap_processed") to the record. Filter to only continue if this field is empty. The Zap's final action sets this field to "yes", so the next trigger is blocked by the filter. Step 3: Use Zapier's built-in loop detection. Zapier automatically detects and stops Zaps that trigger themselves more than 20 times within a short window. However, relying on this is not a fix — it means 20 duplicate records or actions were already created before the block. The filter approach in step 2 prevents any duplicates. Step 4: Restructure to use a different trigger event. If possible, change the trigger to a more specific event that cannot be caused by the Zap's own actions. For example, instead of triggering on "Record Updated" (which fires on any update), trigger on "Record Created" (which only fires on new records). This eliminates the recursion without needing a filter. Step 5: Test with task history monitoring. After applying the fix, manually trigger the Zap once and watch the task history for 2–3 minutes. Confirm only one task entry appears. If a second entry appears, the loop is still active and the filter condition needs to be tightened.