Execution queue collapsed in Cloud

Questions
1

Describe the problem/error/question

Last Thursday 8th of January I ran a workflow that created many concurrent executions. This made my execution queue collapse, which made any new executions go to the queue.

I’ve cleared the execution queue, I’ve restarted our instance. The issue persists. When there’s a new execution in any workflow it gets directly sent to the queue, with start “starting soon” and never runs.

On Friday the 9th I opened a ticket to the n8n support but I still haven’t received an answer and my whole n8n instance has been unusable since then, which is compromising my whole system of workflows in production.

How can I activate my instance again?

Information on your n8n setup

  • n8n version: 2.0.1
  • Running n8n via: n8n cloud
2

If restarting your instant didn’t work, I’m afraid your only option is to wait for support, or to try contacting them again. I would wait at least 1 more day before sending another ticket though, as to not overwhelm them or annoy them.

Can you delete the workflow also that caused the tons of executions? like download the workflow, delete it off the instance, and readd it to see if its bugged.