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 :
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.
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
For you does the n8n log show anything? It could be that the workflow process crashed and the database has just not updated. Restarting the container may help with this.
@Jon not sure about queue mode. But using sqlite.
It is indeed a matter of db not updated as restarting the container has not fixed it. It just shows as running and cannot stop.
I’m guessing there must be possible to just update those records in the database when I click stop if there is no underlying process running.
I’m having the same issue, using n8n version 1.1.1, and postgres as db. Is there already a solution to this problem? Restarting the container didnt change anything.
Rather than restarting can you try stopping the container then starting it again, I have found that with docker sometimes restarting doesn’t fully stop it.
Hi @Jon , thanks for the super-fast response. To make sure, I also did that (I turned off the DigitalOcean droplet and then turned it on again) - but still, the workflow is still shown to be running…
