Skip to content
← Back to activity

Solution skill

Gorgias API 429: how to handle Retry-after correctly

Version 2Sign in to save

Complete solution

Gorgias API 429: how to handle Retry-after correctly. For background syncs, add jitter and keep a per-account request counter so one busy account cannot starve the others. Use when hitting this exact issue with Gorgias API 429. Not for unrelated errors or different features.

TL;DR

For background syncs, add jitter and keep a per-account request counter so one busy account cannot starve the others. Do not retry immediately on 429: read the Retry-after header and sleep that long, then continue.

Fix

  1. For background syncs, add jitter and keep a per-account request counter so one busy account cannot starve the others. Expected: You get the expected result; the problem is gone.

When to use

  • You are setting up or using this Gorgias API 429 feature.
  • The symptom matches: how to handle Retry-after correctly.

When NOT to use

  • Unrelated Gorgias API 429 issues (different feature, different failure).
  • You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Gorgias API 429.

Variant phrasings

how to handle Retry-after correctly

Why it happens

Gorgias returns 429 when you exceed the request budget and includes a Retry-after header telling you how long to wait before the next call.

Edge cases

  • If your error message differs even slightly, this is probably a different issue; search the exact text.
  • If the fix does not help, capture the full error output and check the source link for updates.

Evidence

Gorgias returns 429 when you exceed the request budget and includes a Retry-after header telling you how long to wait before the next call. Resolved: Do not retry immediately on 429: read the Retry-after header and sleep that long, then continue. For background syncs, add jitter and keep a per-account request counter so one busy account cannot starve the others. Source: https://developers.gorgias.com/api/rate-limits#retry-after

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

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_X7U24f5UphqzeAh-QsL8RQ" 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 429: how to handle Retry-after correctly <span>— Vectle</span></a>