Erroe in executions

Questions
1

I have n8n installed on my server (VPS). n8n says I can have an unlimited number of active workflows (currently I have 45). However, today my operations stopped working; they either give an error or remain “queued,” causing all my operations to stop functioning. I would like to know how to proceed.

2

Unlimited active workflows doesn’t mean unlimited execution capacity.If executions stay “queued”, it usually means the worker can’t keep up or is blocked.
Common causes are high CPU/RAM usage, long-running workflows, or queue/worker configuration issues.I’d start by checking server resources and restarting n8n, then look at execution logs to see what’s blocking the queue.

3

Hi @Igor_Santos1 !

When executions remain stuck in “queued”, it usually means the execution engine is blocked, not that you hit a workflow limit.

First, restart n8n to clear any stuck executions, then check if you have long-running workflows (loops, waits, external APIs) occupying the worker.

If the issue comes back, enable queue mode with Redis or increase server resources (CPU/RAM). A single-process n8n instance can queue indefinitely if one execution blocks the main worker.

4

I’ve already restarted my VPS several times, and I’ve also increased the RAM limit, but it keeps queuing in my scenarios.

5

I already did that and it didn’t work.

6

@Igor_Santos1

If this keeps happening even after restarts and more RAM, we need to narrow it down a bit.
Could you please share:

  • a screenshot of the Executions page showing the queued executions (and whether any execution is stuck in “Running”)
  • how n8n is running (Docker or npm, and whether you are using Redis/queue mode)
  • whether the workflows that block contain long loops, Wait nodes, or many external API calls

With this, it will be much easier to identify what is blocking the execution engine.

7

Hi @tamy.santos

I’m taking advantage of this discussion thread to share that I’m experiencing a similar error in my self-hosted n8n, which I describe in the following post:

I tried to make the timeout adjustments they recommended for my Redis, but all my workflows are still queued. And before upgrading to a higher version of n8n, I would like to know if there’s something wrong with my configuration or if it’s definitely an unusual behavior of version 2.0.0.

I don’t know if maybe you’ll see some incorrect setting at first glance that could also be affecting Igor.

8

Quick Fix to Try @Igor_Santos1

Restart n8n:

# Docker
docker restart n8n

# PM2
pm2 restart n8n

# Systemd
systemctl restart n8n

This often clears stuck queues and resets connections.

Hope this helps!