Workflow executions not stopping

Describe the problem/error/question

We have started using n8n at our company to create API endpoints that are called from the browser.
One problem that we are encountering is that, for some workflows, the executions never stop, even though all relevant nodes have been run.
So it ends up looking like this, even though the functionality was successfully executed in ~10 seconds.
image

If you look at the screenshot of the workflow below, you can see that there is a part of the workflow that has not executed, but it is not supposed to, since the if condition failed. My only hypothesis so far is that the issue is related to this.

We have also had some performance issues that may-or-may-not be on the n8n side.
The performance issues could potentially be from having all of these unfinished executions taking up resources. It would give us some peace of mind if this issue was solved, so we could at least rule out this possibility.

Please share your workflow

Information on your n8n setup

  • n8n version: 1.10.0
  • Running n8n via: n8n cloud

Hey @Elias_Sundqvist,

Looking at the screenshot you shared, the part of the workflow executed because the IF condition was false. Do you want it to not execute? I am afraid, I don’t understand what you really mean.

If you look at the screenshot of the workflow below, you can see that there is a part of the workflow that has not executed, but it is not supposed to, since the if condition failed. My only hypothesis so far is that the issue is related to this.

There are a couple of things to consider like the amount of data that is being processed, and the type of data being processed. I would also look at ways to optimize the workflow.

Yes, I don’t want that part to execute, so the the current workflow screenshot looks correct. My question is about why the workflow doesn’t stop.
I thought it was worth mentioning that some nodes in the workflow had not been executed, in case that was related to the issue.

I had the same issue and found that cloning the workflow to a new one + removing the old one made it stop happening. Still don’t know the cause though.

Thanks for the suggestion. Unfortunately it still gets stuck…

Did you try to “always allow output” in the if node? or perhaps you could add an no op nodein between or a second switch, just so it will execute properly.

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