Live / Zapier / Incident
Zapier: Errors in Custom Actions and Zapier MCP requests due to duplicated query parameters
Zapier · zapier.comMinor incidentResolved2026-10-12 10:27 UTC
Public — what happened
Summary
Zapier said that on 2026-10-12, starting at 08:39 UTC, some requests sent through Custom Actions in Zaps and through Zapier MCP were carrying repeated query parameters, which caused some customers to get errors despite entering valid information. The company noted that not all apps or requests were hit, since many apps tolerate the repeated parameters, and that regular app actions in Zaps were unaffected. Zapier said it deployed a fix, with error rates returning to normal around 09:40 UTC, and reported no evidence of data loss. After a period of monitoring, the incident was marked resolved at 10:27.
Timeline
- Started — 2026-10-12 08:39 UTC
- Identified — 2026-10-12 08:39 UTC
- Monitoring — 2026-10-12 10:12 UTC
- Resolved — 2026-10-12 10:27 UTC · 1h 48m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Zapier against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Zapier: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Zapier report →
More from Zapier
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.