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
- Knows 429 means too many requests or rate limited
- Reads docs and honours Retry-After
- Uses backoff and batching
- Ensures failed items are retried, not lost
- Considers asking for higher limits or bulk endpoints
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- What is exponential backoff?
- How would you make sure no records were lost?
Common mistakes
- Retrying immediately in a tight loop
- Letting failed records drop silently
Learn it
- Design an automation that reads supplier invoices from email and enters them into accounting software.
- Your automation created every order twice last night. How do you find and fix it?
- Tell me about an automation you built and how much time it saved.
- How would you build AI triage for a support inbox?
- The AI in your invoice automation sometimes reads the total wrong. How do you stop wrong amounts reaching the accounts?
- A client's old billing software has no API. How would you automate data entry into it?
- An API returns JSON in a different shape from what the next app needs. How do you handle it?
- How do you measure the return on an automation project?
- How would you choose between n8n, Zapier, Make and Power Automate?
- When would you use RPA instead of an API integration?
- Walk me through building a simple automation in n8n or Zapier.
- What is a webhook, and how is it different from polling?
- How do you decide which process to automate first?
- How would you design a WhatsApp assistant for a small business, and when should it hand over to a person?
- Your automation fails halfway through. How do you design for that?