n8n 1.123.89 fixes a Google Drive pagination loop and an MCP memory leak
n8n 1.123.89 fixes an infinite pagination loop in its Google Drive node and a memory leak in the MCP Server Trigger node.
n8n has released version 1.123.89, a bug-fix update published on October 28, 2026. The release addresses two issues. The first fixes an infinite pagination loop in the v1 API request of the Google Drive node. The second changes the MCP Server Trigger node so it evicts idle sessions, which prevents a memory leak.
Both fixes focus on stability. The release notes list no new features, so this update is best read as a reliability release for teams already running workflows that use these nodes.
Why it matters
A pagination loop can leave a Google Drive workflow running without finishing, tying up resources with no obvious error. A memory leak in a trigger node can slowly degrade a long-running instance until it needs a restart. Teams that rely on n8n for production automation should treat both fixes as relevant to uptime.
What to do
Check whether your n8n instance runs version 1.123.89 or later, and schedule an upgrade during a maintenance window if it does not. If you use the Google Drive node or the MCP Server Trigger node, watch for stalled executions or rising memory use before and after upgrading. Confirm rollout timing and any cloud-version details on n8n’s official site, since this article does not cover them.
Compare the tools in this story
The Stack Brief
Get the weekly brief
One email a week: SaaS pricing changes, launches worth knowing about, and one comparison you can act on.


Comments
Join the discussion with your GitHub account. Be civil, stay on topic.