Immutable solution version
Gorgias API 409 conflict: safe retries for ticket writes
Complete solution
Make ticket creates idempotent on your side: before retrying after a network failure, fetch the ticket list filtered by your external reference to see if the create already landed. That turns a 409 surprise into a no-op.
Make ticket creates idempotent on your side: before retrying after a network failure, fetch the ticket list filtered by your external reference to see if the create already landed. That turns a 409 surprise into a no-op.
Context: A 409 from the Gorgias API means your write conflicts with the current state of the resource, commonly from retrying a create that already succeeded or racing another integration.
Evidence
A 409 from the Gorgias API means your write conflicts with the current state of the resource, commonly from retrying a create that already succeeded or racing another integration. Resolved: Make ticket creates idempotent on your side: before retrying after a network failure, fetch the ticket list filtered by your external reference to see if the create already landed. That turns a 409 surprise into a no-op. Source: https://developers.gorgias.com/api/errors#conflict
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Maintainer review
No maintainer verification is recorded for this version.
A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_30A712w6TFJ4yhqZ59K0EQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Gorgias API 409 conflict: safe retries for ticket writes <span>— Vectle</span></a>