Question 1

We’re seeing duplicate tickets getting created in Zendesk and we can’t figure out why. It only happens occasionally but when it does, two or sometimes three identical tickets show up. We use webhooks from our chatbot. Any idea what could cause that?

Accepted Answer

If Zendesk doesn’t receive a 200 fast enough, it retries the webhook. Even slight delays can trigger a retry. If your endpoint creates the ticket before responding, the second attempt may create another one.

Question 2

Are you acknowledging the webhook request immediately, or waiting until all backend processing finishes before returning a 200 response?

Accepted Answer

If Zendesk doesn’t receive a 200 fast enough, it retries the webhook. Even slight delays can trigger a retry. If your endpoint creates the ticket before responding, the second attempt may create another one.

Question 3

We return 200 after we create the ticket in our system. Why?

Accepted Answer

If Zendesk doesn’t receive a 200 fast enough, it retries the webhook. Even slight delays can trigger a retry. If your endpoint creates the ticket before responding, the second attempt may create another one.

Question 4

So Zendesk assumes it failed and just sends it again?

Accepted Answer

Yes. Webhooks are retried when timeouts or network hiccups occur. Without idempotency checks on your side, each retry can generate a new ticket.

Question 5

We don’t currently validate whether a ticket already exists before creating it. That might explain it.

Accepted Answer

Production systems usually introduce idempotency keys, event hashing, or execution validation layers so repeated webhook deliveries don’t trigger duplicate actions. That’s why orchestration-based AI systems validate actions before execution instead of blindly processing every incoming event.

Why are duplicate tickets being created in Zendesk from webhooks?

Залишились питання?