Agent runs (agents.zapier.com) intermittently experiencing 429 errors

What to do

• Check whether your product depends on Zapier. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3h 58m it lasted.

  Anything that failed between 2026-09-21 15:30 UTC and 2026-09-21 19:27 UTC may need a replay.

• Subscribe to Zapier's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=zapier works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Zapier 3

1. investigatingSep 21, 2026, 3:30 PM UTC

   Our team is currently investigating an issue with Agent runs (from agents.zapier.com) intermittently experiencing 429 errors for some customers. We're working to confirm the root cause and implement a fix as soon as possible. AI by Zapier runs are not affected by this incident. If you have any questions or need help, please reach out to our Support team at zapier.com/get-help.

   provider

2. identifiedSep 21, 2026, 5:57 PM UTC

   The team has identified the issue to be an intermittent overload of a service powering: • Agent runs (agents.zapier.com) • AI by Zapier executions As a result, some agent runs and AI by Zapier executions hit 429 errors. We will be working on replaying affected agent runs or Zap runs where possible, and we'll keep this status page updated on our progress. Many thanks for your patience. Our Support team is available if you have any questions, and you can reach them at: zapier.com/get-help.

   provider

3. resolvedSep 21, 2026, 7:27 PM UTC

   The issue intermittently affecting Agent runs and Zap runs using AI by Zapier has been resolved. The confirmed impact window goes from September 18, 2026 at 2:00am UTC to today, September 21, at 15:00 UTC. Our team continues to work with our service provider to prevent this issue in the future, implement better safeguards, and consolidate self-healing capabilities. Some Agent runs from previous days (September 18 to September 20) could not be replayed to avoid duplicate agent executions. For **Agents**, if you want to replay affected runs, go to your[ Agents dashboard](https://agents.zapier.com/bots), open the [All Activity](https://agents.zapier.com/activity) tab to view recent runs, and review the agent runs during the incident window. You can replay any runs that need to be reprocessed by prompting the agent in the chat to retry. For Zap runs using **AI by Zapier**, **no action needed.** Our team has successfully replayed all affected AI by Zapier runs. Many thanks for your patience while we worked through this. If you gave any questions or need help, reach out to our support team at: zapier.com/get-help.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.