Pause and resume evidence operations after a rate limit — what should the operator record?
A rate limit is a reason to pause the affected operation, not to switch identities or repeatedly hammer the same request. Preserve the accepted table and the failed operation's context. Resume only through the documented authorized path, and reconcile any retry result before admitting it as new evidence.
Honor returned retry guidance while preserving the exact last committed operation.
Save the actual error category and any returned retry guidance without fabricating a fixed waiting interval that the service did not provide. Returned guidance may be a retry delay or another documented condition; preserve its actual form instead of converting every rate limit into a guessed fixed schedule.
If the operation remains blocked, hand over the actual state and next review condition rather than changing accounts or claiming the dataset is complete. The handoff can name paused operation and last accepted revision without publishing opaque cursor values or account details in the general incident summary.Record the rate-limit response
Save the actual error category and any returned retry guidance without fabricating a fixed waiting interval that the service did not provide. Returned guidance may be a retry delay or another documented condition; preserve its actual form instead of converting every rate limit into a guessed fixed schedule.
Freeze automatic retries
Mark the operation paused-rate-limit and retain its originating query and last committed receipt, keeping other unrelated authorized work distinct. Do not switch accounts, parallelize the same request or reset a local queue marker merely to evade the pause; those actions exceed ordinary recovery scope.
Validate resume readiness
Check whether the documented continuation remains usable and whether the retry window has actually elapsed before another attempt. An expired cursor can make the original continuation unusable even after a rate limit ends; treat a restart as a distinct chain with its own reconciliation.
Reconcile the resumed output
Compare identifiers and receipt states against the pre-pause checkpoint so an overlapping page cannot inflate the admitted table. If the resumed call succeeds but returns a partial status, transport recovery and coverage recovery remain different outcomes that must both be represented in the ledger.
Document remaining limits
If the operation remains blocked, hand over the actual state and next review condition rather than changing accounts or claiming the dataset is complete. The handoff can name paused operation and last accepted revision without publishing opaque cursor values or account details in the general incident summary.
Keep the boundaries clear.
- Honor returned retry guidance while preserving the exact last committed operation.
- Operational record: Record the rate-limit response. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.