Skip to main content

An API your workflow calls starts returning 429 errors. What do you do?

Automation workflows · Beginner 3

Short answer

429 means too many requests. I would read the API's rate-limit documentation and the Retry-After header, slow down with batching or a delay between calls, and retry with exponential backoff instead of hammering it. If volume truly needs more, I would ask for a higher limit or use a bulk endpoint, and make sure failed items are retried, not lost.

Deeper answer

Rate limits protect the provider's service. A workflow that loops over hundreds of records as fast as it can will hit them. The right response respects the limit rather than fighting it.

Practical steps: honour Retry-After if present; add backoff with jitter; process records in batches with pauses; cache results you fetch repeatedly; and queue failed items for a later retry so nothing silently disappears. Log how often you hit the limit, because a steady increase usually means the business has grown and the design needs to change.

What a strong answer covers

Answer it out loud in the mock interview about 1.5 min

Follow-ups to expect

Common mistakes

Learn it

Call a web API and read JSON

Today's AI turns are used

Lessons, roadmaps, videos, practice cards and the code playground stay free with your account, with no limit.