N8n Cloud: Executions stuck in “Queued / Starting soon” for hours while “No active executions” is shown

Hi everyone,
I’m having an issue on n8n Cloud where production executions are stuck in the queue and never start.

What’s happening
• In Executions, the UI shows “No active executions”
• But many workflows/executions remain in “Queued / Starting soon” for 14+ hours and do not progress
• This affects multiple workflows (not just one workflow)

What works / what doesn’t
:white_check_mark: Manual “Run once” works
:cross_mark: Production executions (normal queue processing) do not start and stay queued indefinitely

When it started
• Started around Dec 26, 2025 and is still happening on Dec 28, 2025 (timezone Europe/Berlin)

What I tried
• Updated to latest (I’m on n8n 2.1.4)
• Restarted everything I can access
• The workspace admin is someone else, so I cannot trigger a full restart from the admin panel myself

Example from my instance

Cloud URL: https://marvintopeople.app.n8n.cloud/
(Executions list previously showed multiple items queued for ~14+ hours, e.g. workflows like “Quali Agent (TOPEOPLE)”, “Execute recruiter actions”, “Calllog Adds new Google Sheet Entry”.)

Debug info

core
• n8nVersion: 2.1.4
• platform: docker (cloud)
• nodeJsVersion: 22.21.1
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: 50
• license: enterprise (sandbox)
• consumerId: 00000000-0000-0000-0000-000000000000

storage
• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning
• enabled: true
• maxAge: 720 hours
• maxCount: 25000 executions

client
• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/143.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2025-12-28T14:37:26.916Z

Instance ID: 1fe41a7853ba4f6b51a10d9661e0082bfdeabb506ddc26fd6d17fe36edd1deb9

Question

Has anyone seen Cloud executions stuck queued while showing no active executions?
What should the admin check (or what should I ask n8n support to reset on their side) to unblock the queue/worker/scheduler?

Thanks!

1 Like

Welcome to the community :tada: @MuhamedBeck

You should go through this thread:

Hello Baseman, i went through the Topic but i couldn’t repoduce it as i have a cloud n8n instance in which i can’t set the docker settings or similar thing mentioned in the solution :confused:

Same issue here!
Running production workflows, its really anoying.

@MuhamedBeck Since you don’t have full admin access, you’ll need to escalate this issue.

  1. Contact n8n Support Directly: Be sure to include:

Your instance URL:

The exact timeframe the problem started (Dec 26, 2025).

The “Debug info” you provided, including the Instance ID:

  1. You should specifically ask your workspace admin to contact n8n support and request a full restart of the workspace from the admin panel.

I hope this helps!

Hi,

I have tried something else and it seems to help.

Check if you have any “Running/Waiting“ workflows. It uses Ram, you can check this here:

Shut down all those workflows, and everything should be working again.

Hey DeanNieuwerf, i tryied to delete all Running (Which are also marked as Starting Soon or in The Queue) and Waiting Exectuions, and still the new ones that are being generated from my scheduler still get stuck in a new waiting Queue. Even Thoug i have 0/50 Active Executions.

Another problem is, that I am on the Cloud Version. So I have no Access to the docker Configurations or similar.