ERR_CIRCULAR_REFERENCE on Make.com: Circular reference detected. Root cause: The workflow triggers itself in a loop — for example, an automation that updates a record triggers a webhook that fires the same automation again. Without a termination condition, this creates an infinite execution chain that consumes API quota and eventually gets blocked by the platform. Step 1: Map the full trigger chain. In Make.com, open the scenario and trace every module. Draw or note the path: what triggers the scenario, what each module does, and whether any module updates a record in the same system that triggered the scenario. The circular reference will be visible as a loop in this map. Step 2: Add a guard field to break the loop. The most reliable fix is a "processed" boolean field on the record. When the scenario runs, the first action sets this field to true. Add a filter at the start of the scenario that only continues if the field is false. This means the second trigger (caused by the first run) will be blocked by the filter and will not re-execute. Step 3: Use Make.com's built-in loop limit. In the scenario settings (the clock icon), set a maximum number of cycles. This is a safety net, not a fix — it stops runaway execution but does not address the root cause. Set it to 1 for scenarios that should never self-trigger. Step 4: Separate write and trigger operations into different scenarios. If the circular reference is unavoidable (e.g. you must update the same record you're watching), split the work into two scenarios: one that reads and processes, and one that handles the write. Use Make.com's webhook or a queue table to pass data between them without creating a direct trigger loop. Step 5: Test with execution history. After applying the fix, run the scenario once manually and check the execution history. Confirm the scenario ran exactly once and did not re-trigger. Check the guard field on the test record to verify it was set correctly.