Workflow won't stop and can't be stopped

Questions
1

Hi,

Describe the issue/error/question

I’m having trouble on one of my workflows. It never stop and have many instances running, causing performance issue after some hours (i think).

image
image342×923 36.9 KB

If I click on “Stop execution”, it result to a 524 HTTP error code (timeout error).

I’m wondering how can we force/kill these blocked executions. It is happening on some other workflow, but not that much as this one.

What is the error message (if any)?

If I click on “Stop execution”, it result to a 524 HTTP error code (timeout error).

Please share the workflow

Share the output returned by the last node

No output because the execution is still running…

Information on your n8n setup

  • n8n version: 0.222.0
  • Database you’re using (default: SQLite): How can I be sure ? I think PostgreSQL
  • Running n8n with the execution process [own(default), main]: default
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker compose (customized)
2

Hey @Locos,

This is something we are aware of and should be resolved in the next release, For now it would be worth using an earlier version of n8n like 0.220.1

2 Likes
3

Hi,

Does the v0.222.1 should fix it ?
For now, I’ve tested and still have unfinished executions.

4

Hey @Locos,

It should fix some issues but not specifically that one.

5

Hi @Jon ,

I’m getting less workflow in this case. Now I’m checking for some of them, if they’re already executed in background (using old rest api).

But today, I just had a similar issue. One of my workflow, has reached :
image

So it will not be executed anymore, because it is running constantly. We can’t stop/remove it.

Did you found the cause of this trouble ? If yes what we’ve to take care about ?

EDIT : I’ve tried to stop the execution, remove the execution through the web interface or the API, it is always telling me that the resource doesn’t exist. But it is listed.

Thanks

6

Hey @Locos,

What version of n8n are you running now?

7

@Jon the v0.225.2, not yet updated to 0.226.2

8

Have you tried restarting n8n? It could be that it wasn’t able to update the database.

1 Like
9

Hello,
we had the same problem, we solved it by opening the db and deleting the row from the table “execution_entity”

10

Are there any instructions on how to do this?

11

Hi @Stiehla - you might want to take a look at my two posts in this thread, which will link you to a tool you can use to access the database, and what you’re looking for:

There’s a post underneath with screenshots, as well :+1:

12

Oh ok! So you mean, if I get some “Database is locked/busy”, means some workflow cannot stop them current execution and have a pending status

Good to know!