Provider
ZapierIncident detail
Errors in Custom Actions and Zapier MCP requests due to duplicated query parameters
Timeline window
to
Get alerted the next time Zapier breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Identified
We've identified an issue where some requests made through Custom Actions in Zaps or Zapier MCP include duplicated query parameters. Because of this, some customers may see errors even when their inputs are valid. Not every app or request is affected, since many apps handle duplicate query parameters without issue.
Standard app actions for connected apps that run in Zaps are not affected. We'll update this page as soon as we have more information.
If you need help, please reach out to our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help").
Monitoring
A fix has been deployed that stops Custom Actions and Zapier MCP requests from sending duplicated query parameters. Error rates on affected requests dropped to normal immediately after deployment (~09:40 UTC).
Not every request failed during the issue, and we have not identified evidence of data loss. If a connected app behaved unexpectedly during this window, please reach out so we can take a closer look.
We’re continuing to monitor and will post a final update within 24 hours.
If you need help, please reach out to our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help").
Resolved
The issue causing duplicated query parameters on some Custom Actions and Zapier MCP requests has been resolved.
Starting October 7, a deploy caused some outbound requests to include duplicate query parameters, which a subset of connected apps rejected even when inputs were valid. Not every request was affected, and standard app actions in Zaps were not impacted.
A fix was deployed on October 12 at 09:40 UTC to remove the duplicated parameters, and error rates returned to normal immediately. We’ve been monitoring since and have not identified any further impact or evidence of data loss.
We’re reviewing the change that introduced this to prevent similar issues going forward.
If you experienced errors during this window and still need help, please reach out to our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help").
Keep exploring
More from Zapier
Neighboring incidents on Zapier's timeline and the rest of their record on OutageDeck.
- zapier-dev-files.s3.amazonaws.com is tagged as "dangerous site" by GoogleMinor
- Logging into Zapier using Facebook or Microsoft SSO shown a blank page after authentication.Major
- Azure DevOps connections failing: expired OAuth client secret (AADSTS7000222)Minor
- Agent runs (agents.zapier.com) intermittently experiencing 429 errorsMinor