We’re facing an issue on n8n Cloud where executions appear to be stuck at the platform level.
What happened:
Due to a misconfiguration, one of our analytics workflows was triggered repeatedly (page refresh–based trigger).
Within ~30 minutes, this caused 1,500+ executions, many of which failed.
As soon as we noticed, we disabled all related workflows to stop further triggers.
Current problem:
Since then, all executions are stuck in Queued / Starting soon, even:
Older workflows that previously worked fine
Simple/manual test executions
Some executions have been queued for 1–2+ hours
Disabling workflows did not resolve it
What we’ve already done:
Turned off all analytics-related workflows
Stopped any possible external triggers
Avoided re-running workflows to prevent further load
Observation:
This looks like a stuck execution queue / worker deadlock, rather than a workflow logic issue, since even unrelated workflows are affected.
Request:
Could someone from the n8n Cloud team please:
Check this instance for stuck workers or queued jobs
Restart / redeploy the instance if needed
Clear any blocked executions at the infrastructure level
I’ve attached a screenshot showing the queued executions for reference.
Thanks in advance — happy to provide any additional details if needed.
You’re most likely hitting a stuck or blocked execution queue on n8n Cloud, not a problem with your individual workflows, especially after a sudden spike of around 1,500 executions in a short time.
On n8n Cloud there is a concurrency limit, and when that limit is exceeded or the queue gets into a bad state, executions can remain in “Queued” indefinitely. Other users have seen the same behaviour and a simple workspace restart from the Cloud UI cleared the queue and everything started running again.
Since this is Cloud, you can’t clear the queue yourself. First try restarting your workspace from the n8n Cloud dashboard, as a workspace admin. If that doesn’t fix it, contact n8n Cloud support and explain that after a large spike all executions are stuck in “Queued/Starting soon”, even manual ones, that you already disabled the triggering workflows, and ask them to restart the workspace and clear any blocked executions on the infrastructure side.
