URGENT: Loop Over Items Node Crashed Entire Cloud Workspace - Bad Gateway

[Moncho]

Title: URGENT: Loop Over Items Node Crashed Entire Cloud Workspace - Bad Gateway Error

Category: Bug Reports / Cloud Issues

---

CRITICAL PLATFORM FAILURE - IMMEDIATE ESCALATION NEEDED

My n8n Cloud workspace is completely unusable due to what appears to be a severe platform bug with the Loop Over Items node.

Current Status:

• Complete workspace failure - cannot access anything
• Bad Gateway error on signin URL: https://picklewickel.app.n8n.cloud/cloud/signin
• Admin panel broken - redirects to broken dashboard
• Workspace has been down for hours

What Happened:

1. Configured a Loop Over Items (Split in Batches) node with standard settings (Batch Size: 1, Reset: ON)
2. Node got stuck in infinite execution loop
3. Workspace crashed with 503 errors
4. Now getting Bad Gateway errors - cannot even reach signin page

Impact Beyond n8n: This bug didn’t just crash n8n - it caused a cascading system failure:

• n8n’s infinite loop spam-called my production API endpoints
• 35+ API calls per second for 35 minutes straight
• Burned through my entire Vercel function quota
• Cost me money on external services

This is a CRITICAL PLATFORM BUG:

• A simple workflow node configuration should never break an entire workspace
• The Loop Over Items node appears to have no safeguards against infinite loops
• Infrastructure should recover gracefully, not stay permanently broken

Support Ticket: #7632925 (standard support queue is too slow for this severity)

I am a paying Cloud customer with time-sensitive work completely blocked by this platform failure.

Request: Please escalate this to your infrastructure/platform engineering team immediately. This is not a “how do I configure this” question - it’s a critical service reliability issue.

Has anyone else experienced Loop Over Items nodes causing complete workspace crashes? This seems like a serious platform stability bug.

@n8n_team - urgent escalation needed.

[Erick_Torres]

Add an explicit exit condition (If + Conditional Reset)
If Reset is enabled, define the condition to restart only when necessary. Example:

Reset = {{ $prevNode.name === 'Check Completed' && !$node["Loop Over Items"].context.noItemsLeft }}

This prevents restarting after there are no more pending items.

Using expressions like {{$node[“Loop Over Items”].context.noItemsLeft}} lets you know if the loop still has more items and act before processing the last empty iteration.

Handling the extra empty iteration within a Code or If statement:

if (!$item.json || Object.keys($item.json).length === 0) {
return []; // ignore this iteration
}