Workflow is loading to infinity and not running

Questions
#1

Hello,

I deployed the n8n application with postgres database in my own server and everything is OK.
But, most of the time, when I run a workflow, it stays loading to infinity. (sometimes it works fine)

When I tried to stop it, I got this error :

Capture d’écran 2020-12-23 à 11.13.28
Capture d’écran 2020-12-23 à 11.13.28814×408 25.5 KB

And in the server log I got this message :

Error: The execution id "7" could not be found.
    at /usr/local/lib/node_modules/n8n/dist/src/Server.js:1031:23
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /usr/local/lib/node_modules/n8n/dist/src/ResponseHelper.js:71:26

It was a very simple workflow, just to test.

Does any one has an idea, what can be the problem causing this error ? is there any missing configuration that I should do it when deploying the n8n app in my server ?

Thanks, Best regards,

#2

Here is the workflow I’am testing

Capture d’écran 2020-12-23 à 11.30.46
Capture d’écran 2020-12-23 à 11.30.461390×1022 33.7 KB

#3

Welcome to the community @Slaheddine_Ben_Zina!

I assume that the workflow actually finishes but because of connection issues that information gets lost. If you click on “Executions” in the menu on the left side. Does it display the workflow running there? If not, then it does actually not run anymore and would explain why it could not be stopped.

1 Like
#4

Thank you for your answer.
I understand. It is totaly normal that I can’t stop a not running workflow.
What I want to understand, why that information is lost ? and the job stays loading to infinity. Is there a configuration that I should do ?
Here is a small video to more explain my issue : https://vimeo.com/494131993

#5

How are you running n8n? Locally/Server, Docker/npm/Git, any reverse proxy inbetween, operating system, …?

#6

It is deployed on a server, with docker and it is managed by Kubernetes.
I figure out the problem, I was using 2 replicas pods and changed that to 1 replica.
The app now is working fine.
I think that some states/data were lost between the tow pods.

#7

Yes that makes sense. That would cause a lot of problems.