Hi We have a problem that we have a number of processes running and we can’t stop them and they don’t get executed. Is there any solution for this ? [Screenshot 2020-04-28 at 16.46.33]

I guess you are running all workflows in the main process by setting EXECUTIONS_PROCESS=main because else that should not be able to happen as it simply kills the process and it can stop it no matter what. The error #524 is a apparently a timeout. So it looks like it tries to stop the workflow but …

Hi Yes I think we changed the EXECUTIONS_PROCESS=main to prevent memory runaway, based on our discussions. We needed to restart the N8N so I can not trace where it did get stuck. The workflow has just 3 nodes, a receiving webhook, a switch and HTTP post. We have to monitor and see why it happens…

How long do you expect these processes to run? Would you be able to share your workflow with us?

hi! It is expected / (and normally does) last about a second. I try to can share it but it needs to be without credentials. Here is at least a screenshot of workflow [Screenshot 2020-04-29 at 07.58.11]

It did happen again on another workflow which looks very similar. We have added continue on fail on the last node. Is there any way to make the process kill itself if it doesn´t work. The interesting thing is that it seems that workflows have succeeded and failed (see the second picture) [Scre…

If you reload n8n website and then then go to “Executions” does it then still display them? Because I think that the “message” that informs the UI that the workflow did finish maybe simply gets lost because of connection problems and that is why the frontend still thinks that it is running even thou…

Hi Yes it appears even when reload and it appears on both mine and other computers when logging into the same instance. So my feeling is that it not frontend related. It started to happen after we change the setting to main as you descried it to prevent the memory spike.

I can reproduce it. Will check how it can be fixed.

Found the issue. Will try to release a new version with the fix later.

Hi We got this problem today again We have the setting to that it should not start parallel processes. Version 0.74.0 Is there any way we can kill it? Kind regards Mattias [Screenshot 2020-08-06 at 17.11.32]

Problems with stopping processes

Questions

jan April 29, 2020, 10:53pm 11

Fix got released with n8n@0.65.0

Sent binary data example

Topic		Replies	Views
Bugged workflow execution process Questions execute-workflow , executions , stop-and-error	4	168	January 10, 2025
Workflow executions not stopping Questions core	5	1284	October 26, 2023
Workflow won't end only after killing the process Questions development , custom-node	5	1417	September 1, 2022
Problem stopping execution Questions	12	5403	June 2, 2025
N8n behavior on k8s setup Questions deployment , scaling	2	767	December 22, 2022

Problems with stopping processes

Related topics