MCP tool calls fail with new toolCallId and old workflows stop running after update Planned
Planned: Scoped for the next release.
Claim the n8n page
Claiming is free. You prove you work at n8n with an email address at n8n.io; Friction sends a link there.
- 69 reports from users of n8n
- 80 separate source threads
- 2019–2026 the years they cover
- Most recurring theme: AI agents lose or mishandle tool-call results, 6 threads
These are public today, under your product's name. A reply from n8n sits under the report, on the record, marked as verified at n8n.io: the next person who reads it sees you answered.
What n8n would post on the top report
Built on the report people repeat most on this page. Nothing appears until you post it.
A first reply, under the report
A board post, with a public status
A changelog entry, linked to the report
Fixed: MCP tool calls fail with new toolCallId and old workflows stop running after update
Resolves: MCP tool calls fail with new toolCallId and old workflows stop running after update
Reports are not edited or removed by the vendor; a wrong one is flagged and reviewed within 3 working days. More on what vendors get.