diff --git a/references/api/api_core_concepts/handling-rate-limits.mdx b/references/api/api_core_concepts/handling-rate-limits.mdx
index 1c2b705..6eab693 100644
--- a/references/api/api_core_concepts/handling-rate-limits.mdx
+++ b/references/api/api_core_concepts/handling-rate-limits.mdx
@@ -19,7 +19,7 @@ Quote traffic is the next place to look. `/quote` carries the tightest default l
 
 Validation belongs on the client too. Amounts below Relay's minimum come back as [`AMOUNT_TOO_LOW`](/references/api/api_core_concepts/handling-errors), so a sub-cent value a user types should fail your own check before it turns into a quote call. Where your interface already knows the user's balance, apply the same treatment to amounts they can't cover.
 
-If you poll for status, widen the interval and stop polling once a request reaches a terminal status (`success`, `failure`, or `refund`). When you need many records at once, [`GET /requests/v3`](/references/api/get-requests) retrieves them in a single filtered call instead of one call per request ID.
+If a polling request returns a `429` response, retry with exponential backoff instead of retrying immediately.
 
 ---