Node No operation continues running

Does anyone know why if the flow reaches the No Operation node it continues running for so long?

Information on your n8n setup

  • n8n version: 1.8.2
  • Database: Postgres
  • Running n8n via (Docker, npm, n8n cloud, desktop app): CapRover

Hi @Mauricio_Bueno

Welcome to the community!
I have never seen this before.

Not sure what CapRover is, could you give a bit more info and also maybe update to the latest version just incase it was fixed. As I do not have any instance on 1.8.2 I would not have noticed this specific issue. And I use a lot of no operation nodes. :slight_smile:

1 Like

I’m seeing the same behaviour using 1.9.0. The weird thing is that it is not always happening, so maybe 1 out of 4 happen this.

I also tried to delete the no operation node and it keeps doing the same.

One thing that we have in common is that the previous node is the “IF” node.

n8n Version 1.9.3
two servers vith various configs
Every config and servers is infinite running after update

(scenario executions view)
(executions view)
scenarios which not contains NoOp node ending fine.

Hi folks, I am so sorry for the trouble. As per this related thread, can you try upgrading to [email protected] or later and confirm if you’re still seeing this problem for new executions started after the upgrade?

Got the same problem here.

Running n8n selfhosted on Cloudron
It looks like version 1.9.3?!
Now I got it: :man_facepalming: 1.11.1 is much higher than 1.9.3 :crazy_face:
Sorry… I have to wait for cloudron updating n8n

@MutedJam BTW: when will this version 1.11.1 or higher will be available as “latest”?

Hey @RoP,

Welcome to the community :tada:

We marked 1.11.1 as latest probably a few minutes after you posted :slight_smile:

1 Like

Hm, at githup it ist still status “pre-released” for 1.11.1

Cloudron pulls updates form this place.

Hey @RoP,

You can find our latest and next versions in our docs here: Release notes | n8n Docs

On npm here: n8n - npm

And on DockerHub here: Docker

The GitHub release is something we don’t yet have in full sync with everything else but assuming Cloudron is using the lastest tag a redeploy should get you the newest version. I would recommend keeping an eye on our release notes as that will have the latest version on it.

1 Like

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