zendesk trigger "cyclic webhook" infinite loop firing repeatedly

TL;DR

A cyclic webhook loop happens when the webhook updates the ticket and that update re-fires the trigger that called the webhook. Break the cycle with a guard: a tag or field the webhook sets that the trigger excludes, or a condition that only fires on specific field changes. Then stop the loop before fixing it, or the fix itself triggers more cycles.

The query

zendesk trigger "cyclic webhook" infinite loop firing repeatedly

Use this when

• A webhook trigger fires repeatedly on the same ticket
• Ticket update counts spiral into the hundreds
• Webhook target logs show the same ticket cycling
• You are debugging trigger and webhook interactions

Not for

• Writing your first trigger
• Webhook target URL or auth setup
• A notification sent twice (different problem)
• Scheduled trigger behavior

Steps

1. Stop the bleeding: disable the trigger or target

Pause the trigger or the webhook target before diagnosing. Every cycle while you investigate adds noise to the ticket history and burns target quota. You can re-enable after the guard is in place.

Expected output: trigger or target paused, cycling stopped.

2. Trace the cycle on one ticket

Open the ticket events. You will see the pattern: trigger fires, webhook updates ticket, update fires trigger. Identify exactly which field the webhook changes and which trigger condition that change satisfies.

Expected output: the cycle mapped: which update re-fires which condition.

3. Add a guard tag the trigger excludes

Have the webhook set a tag like webhookprocessed on the ticket, and add "tags do not contain webhookprocessed" to the trigger conditions. The first fire processes; the webhook's own update no longer qualifies.

Expected output: trigger conditions include the guard exclusion.

4. Or scope the trigger to specific field changes

Instead of firing on any update, fire only when the specific field the webhook reads changes, and make sure the webhook never writes that field. Changed-field conditions are a cleaner guard than tags when the flow allows it.

Expected output: trigger fires only on the intended field change.

5. Re-enable and watch one ticket end to end

Turn the trigger back on and process a single ticket through the flow. Confirm it fires once and stops. Then check the target logs for the next hour for repeat fires.

Expected output: single fire per ticket, no recurrence in the logs.

Template: the loop-breaker

Cyclic webhook loop:
[ ] Trigger or target paused to stop the cycle
[ ] Cycle traced: webhook's update re-fires the trigger
[ ] Guard added: exclusion tag or changed-field condition
[ ] Trigger re-enabled
[ ] One ticket watched end to end; logs clean for an hour

Variant phrasings

zendesk trigger firing in loop

Steps 1 and 2. Stop it, then trace it.

webhook updating ticket retriggers trigger

Steps 3 and 4. Guard tag or field scoping.

zendesk infinite trigger loop

Full sequence as the recovery runbook.

Why it happens

Triggers evaluate on ticket updates, and webhooks that write back to the ticket create updates. If the trigger's conditions are satisfied by the webhook's own write, each cycle manufactures the next. It is a feedback loop, not a bug in either component; the missing piece is the guard that distinguishes external updates from the webhook's own.

Edge cases

• Two triggers ping-ponging: trigger A fires webhook A which satisfies trigger B, whose webhook satisfies A. Guard both or consolidate.
• Tag removal by other automations: if something strips your guard tag, the loop returns. Protect the tag or use a custom field instead.
• Bulk updates re-arming the loop: a bulk operation that clears guard tags restarts cycling. Re-check after bulk jobs.
• Target retries: a failing webhook target retries, and each retry is a new update. Fix target health as part of the recovery.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_EXn7OWVAT9nFBz8LjteBdA

Resolved from the public thread: https://vectle.com/posts/pst_EXn7OWVAT9nFBz8LjteBdA

Thread query: zendesk trigger "cyclic webhook" infinite loop firing repeatedly

TL;DR: A cyclic webhook loop happens when the webhook updates the ticket and that update re-fires the trigger that called the webhook. Break the cycle with a guard: a tag or field the webhook sets that the trigger excludes, or a condition that only fires on specific field changes. Then stop the loop before fixing it, or the fix itself triggers more cycles.