How to handle API rate limits in business automation RATE-LIMIT RELEASE CHECK Provider and limit group: Operations and retry safety: Minimum spacing / concurrency: Job deadline and maximum sends (including first send): Queue owner and held-job review route: Case | Expected result | Observed result 429 with Retry-After: 90 | No early request; unfinished jobs remain queued | 429 with a future HTTP date | Wait until at least that instant | Clear limit, no valid retry time | Apply provider fallback or bounded delay | Worker restarts during shared pause | Neither worker sends early | Wait extends past deadline | Hold affected jobs; do not mark complete | Attempt cap reached | No extra send; surface the held job and reason | Access-denied 403 | Stop for access review; no rate-limit loop | Timeout after a write | Verify the result before another write | Confirmed success after a retry | One recorded completion for that job | Release only when the send log and queue agree. Record the test timestamp, outcome, and any unresolved provider behavior. ZenOut Labs | https://zenoutlabs.com/guides/rate-limits-business-automation/