Changing n8n to Queue mode - previous queued executions are not getting triggered

Questions
1

Describe the problem/error/question

I needed to change the configuration on an n8n instance that was using the default Execution Mode. This instance has more than 200.000 pending executions. The idea was to change the Execution Mode to queue mode and deploy as many workers as would be needed to execute all the pending executions. What is happening is that once I change the Execution Mode to queue mode, all the previous queued executions will not get triggered. The query for pending executions function returns nothing. If new executions are created, for example using webhooks or manually, they are correctly executed on the workers.

Information on your n8n setup

  • n8n version: 1.53.2
  • Database (default: SQLite): postgresql
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: Ubuntu
2

Hey @Carlos_Sancho,

Welcome to the community :cake:

The previous exections won’t be in the Redis database for the workers to pick up and the main instance won’t process them so in theory those executions would never run and may already have failed and the database just might not be updated.

It is always best to start with no executions waiting if you are going to move to queue mode to avoid running into issues like this.

3

Thanks for your reply @Jon.
Do you know if there is something I can do directly to the database to change the status of those Executions so they are queued again?

4

Hey @Carlos_Sancho I am not aware of anything that would put them back into a queued state it would also depend on if the data was still around or if it had been purged.