**_{_{}} Avoid retrying all 403, 404, and 410 responses**

[Trustinbtc999-hue]

Avoid retrying all 403, 404, and 410 responses

A 403 commonly denotes a primary or secondary rate limit, for which the REST troubleshooting guidance requires waiting for retry-after or the rate-limit reset rather than refreshing installation access; repeated requests can lead to an integration being banned. A 404 can indicate a bad path or missing resource, and a 410 means the resource or endpoint is gone, so neither is generally made retriable by refreshing access. Split these cases by status and response headers instead of instructing readers to retry all three.

Useful? React with 👍 / 👎.

Originally posted by @chatgpt-codex-connector[bot] in Comrrflex/docs#1 (comment)