Minor incident
Zapier: Errors in Custom Actions and Zapier MCP requests due to duplicated query parameters
Oct 12, 2026, 08:39 UTC
started
10:27 UTC
resolved
1 h 48 min
duration
Current status of Zapier: Partial outage — live Zapier status
Timeline
- Oct 12, 2026, 08:39 UTCidentifiedWe'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").
- Oct 12, 2026, 10:12 UTCmonitoringA 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").
- Oct 12, 2026, 10:27 UTCresolvedThe 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").
Updates as published by Zapier.
Other services with incidents at the same time
This was part of a wider event: 12 services reported incidents within the hour.
- Jimdo 09:34 UTC · Webmail Outage
- IPRoyal 09:29 UTC · IPRoyal Customer Dashboard issues
- Aircall 09:29 UTC · Calling Issues
- Mercado Pago 08:56 UTC · Point - Approval Anomaly - MLB
- Cloudflare 08:52 UTC · Elevated errors in Los Angeles (LAX)
- Sage 08:41 UTC · Banking Service - Partial Outage
- GoCardless 08:39 UTC · Email delivery issues affecting Yahoo and AOL addresses
- PagBank 08:38 UTC · System unavailable:
- Cardiff University 08:31 UTC · Intermittent issues accessing the SIMS Client via RAS
- Telnyx 08:31 UTC · Email API messages rejected with gw_reject// injection_failed
- Sumsub 08:30 UTC · Applicants incorrectly rejected due to face matching issue
- Make 08:23 UTC · Failing scenarios with "Scenario" app
- Domainkeskus 08:13 UTC · Sähköpostien suodatuksessa ongelmia
- iAdvize (HA) 08:06 UTC · P1 - Impossible to open conversation
- SEEK API 08:05 UTC · Intermittent timeouts across all services
More Zapier incidents
- October 23, 2026 Connection errors affecting Salesforce Pardot Zaps
- October 22, 2026 Security updates in progress for third-party software components
- October 22, 2026 Assessment of recently reported PHP vulnerabilities
- October 21, 2026 Delayed real-time updates in Zapier Tables
- October 21, 2026 Upstream errors with the BambooHR integration
- October 16, 2026 Errors publishing Zaps from Guided Templates with app approvals enabled