Problem stopping execution not exist in queue

Questions
1

Hi friends,

Describe the problem/error/question

in our n8n cluster EXECUTIONS_MODE=queue
Our n8n setup contains redis(3 pod statefulset), n8n main( 1 pod deployment), n8n worker(5 pod deployment) and postgresql database(3 pod statefulset) containers.

on n8n web UI we saw too many executions are running since two week ago. We wanted to stop the executions but we couldnt stop. The error message is “could not stop as it is no longer in queue”
We have changed state of this executionId to failed by modifying execution_entity table in database. Now executions became failed on n8n web UI. We wonder the root cause of this problem.

What is the error message (if any)?

The error message is “could not stop as it is no longer in queue”

Please share your workflow

image

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

n8n_error
n8n_error1747×882 35.6 KB

Information on your n8n setup

  • **n8n version:n8nio/n8n:1.12.2
  • **Database (default: SQLite):postgresql
  • **n8n EXECUTIONS_PROCESS setting (default: own, main):default
  • **Running n8n via (Docker, npm, n8n cloud, desktop app):openshift
  • **Operating system:openshift 4.12
2

Hey @Aydemir,

I would start with an upgrade we have done some work on queue mode issues since 1.12 and one of them sounds familar to what you are seeing but if you check the logs for your workers and your main instance there could be some errors that are useful for working it out but an upgrade is the place to start to rule out anything already fixed.

3

Hi Jon,

Which version do you recommend to upgade from 1.12 to ?

Best Regards

4

Hey @Aydemir,

I always recommend whatever the newest version of n8n is, At the moment that is 1.31.0.

5

thanks alot

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.