Prompt · Developer Tools

Retry Logic Review

Reviews or designs retry, backoff, and idempotency for a flaky integration.

Have ready: Paste the integration code or describe the flow

Fill in · 4 fields

PASTE THE INTEGRATION CODE OR DESCRIBE THE FLOWWHAT SERVICE YOU CALL, ITS SLA, RATE LIMITS, IDEMPOTENCY SUPPORTTIMEOUTS / 429s / 500s / NETWORK ERRORSMY LANGUAGE

Your prompt

Review the retry behavior of this integration. Then fix it.

Code or flow description:
[PASTE THE INTEGRATION CODE OR DESCRIBE THE FLOW]
Downstream: [WHAT SERVICE YOU CALL, ITS SLA, RATE LIMITS, IDEMPOTENCY SUPPORT]
Failure modes seen: [TIMEOUTS / 429s / 500s / NETWORK ERRORS]

Deliver:
1. Verdict on the current approach: what breaks under real failure (retry storms, duplicate side effects, unbounded waits).
2. The corrected retry policy: max attempts, backoff algorithm with jitter (show the math), per-attempt timeout, total deadline.
3. Idempotency design: how to make retries safe for THIS downstream (idempotency keys, dedupe, or "safe to retry because...").
4. Circuit breaker: when to add one, with thresholds justified by the downstream's behavior.
5. What to alert on: the metric and threshold that pages a human.

Show code for the retry wrapper in [MY LANGUAGE].

Paste it into Muse or any assistant. Blank fields stay as [brackets].

More like this

Webhook Handler Template