From the daily brief · Automation
Zapier fixes bug that broke some Custom Actions and MCP requests from Oct. 7 to Oct. 12
If a Zap uses a Custom Action or an AI assistant runs Zapier through MCP, some runs may have failed for five days and need redoing by hand.
- What happened
Zapier says a deploy starting October 7 caused some outbound Custom Actions and Zapier MCP requests to include duplicate query parameters, which a subset of connected apps rejected even when inputs were valid. A fix went out on October 12 at 09:40 UTC; Zapier says standard app actions in Zaps were not affected and it has found no evidence of data loss.
- What it means for a 10-to-50-person business
Most Zapier users can skip this. Standard app actions, the prebuilt steps most Zaps use, were not affected. It matters only if a Zap uses a Custom Action, the step you build yourself against an app's API, or if you connect an AI assistant to your apps through Zapier MCP. Example: a 15-person accounting firm uses a Custom Action to create a client record in its practice-management software for each intake form. Assume 6 new clients a day. Over the four working days from Wed. Oct. 7 to Mon. Oct. 12, up to 24 records may never have been created, if that app was one that rejected the duplicated parameters. Zapier says not every app or request failed, and its status page does not say failed runs were retried. So the gap is yours to find. The likely damage is quiet: an intake that never reached the client list, or an invoice or job that was never created.
- What to do
- Ignore
Nothing needs changing, but if any Zap uses a Custom Action or you use Zapier MCP, filter Zap history for errored runs from Oct. 7 to Oct. 12 this week and rerun or re-enter the ones that matter.
- What it costs
What it costs - Zapier plan or setup change
- $0
- Checking Zap history for Oct. 7–12 errors
- 30 min (≈ $25 at $50/hr)
- Re-entering missed records, assume 24 × 3 min
- 1.2 hrs (≈ $60 at $50/hr)
- Doing nothing
- $0 now; any requests rejected Oct. 7–12 stay undone until someone notices a missing record
- Sources
- status.zapier.com (primary) · Zapier Support: get help
Questions owners ask
- Were my normal Zaps affected?
Zapier says standard app actions for connected apps in Zaps were not affected. Only Custom Actions and Zapier MCP requests were affected, and only with some apps.
- Did Zapier lose any of my data?
Zapier says it has found no evidence of data loss. The risk is requests that were rejected and never completed, not data that was deleted.
- Who do I contact if something still looks wrong?
Zapier asks affected customers to contact its support team at zapier.com/app/get-help.
Three to five of these, every weekday morning.
Related
Brief · Nov 2, 2026
Zapier now bills AI and code steps in tasks, at rates set by model and runtime
If your Zaps use AI or Code steps, your task count can rise without any change to your plan price, and…
Brief · Oct 28, 2026
Zapier moves AI steps and code to task-based billing; Professional from $19.99/mo
If your Zaps use AI or Code steps, each run may now use more tasks, and a busy month can tip into Zapier's…
Brief · Oct 28, 2026
Claude Sonnet 5.5 errors hit claude.ai and the API for 35 minutes on Oct. 27
A short Anthropic outage is no reason to switch vendors, but any automation that called Claude this morning…
Brief · Oct 28, 2026
n8n 3.0 beta out Oct. 27 with breaking changes; stable release due early December
If job syncs, reminders or invoice flows run through n8n, the 3.0 upgrade can break them, and there is no…