This has been going on for the past few versions now.
What is the error message (if any)?
The workflow just appears to be running BUT doesnt run at all - indefinitely. You cant stop it (gives and error message about cant stop).
The only solution is
Save the workflow
Refresh the page
Then if you do what you did previously that didnt work - it just works now !
Getting tired of this drill now as you start to build 100 workflows and keep changing them, so I thought I would bring it up.
Please share the workflow
(Select the nodes and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow respectively)
Share the output returned by the last node
Information on your n8n setup
**n8n version:0.205.0 and earlier too
Database youâre using (default: SQLite):
Running n8n with the execution process [own(default), main]:
**Running n8n via [Docker, npm, n8n.cloud, desktop app]:docker
@maxT I can confirm itâs still (kinda) there (just updated to 0.207.0). When I click âExecute Workflowâ the On clicking âexecuteâ node says âWaiting for you to create an event in Manualâ - you canât see the workflow running.
When saving of manual executions is enabled and I hit the stop button, I can see the workflow executed and I can examine nodes and outputs.
When saving of manual executions is not enabled and I hit the stop button, it says âProblem stopping execution, Execution not foundâ.
Thanks @maxT for the attention to this - I am going crazy with this.
I will update to 0.207 on a test instance and check - will report back.
In my case the workflow doesnt run - it doesnt run, stop - nothing and save+refresh is the only answer
@treyr When you replace the GET HTTP with something that creates a record, row, contact (or anything else really) youâll see the record is created so the workflow actually gets executed. We just canât see it in the Editor UI.
@antitalent - thanks - I dont think I have added or changed data so havent seen it - will test that out too.
I just now - create workflow - save - refresh - run - save, refresh - run âŚ
Hey @treyr, I tried to reproduce your error but was not able to (tested in a few different versions). Does this happen every time for you? Or just under specific conditions?
Yep, saw the video but was not able to reproduce at first. I managed to reproduce it by now (by throttling my internet speed). Thanks so much for finding and posting this!
@Niklas_Hatje - thanks.
I dont think my issue is internet speed related though
Have a 1Gbps connection and the server is on DigitalOcean and speeds are consistently > 500 Mbps between the browser and the server.
But I am glad you can reproduce this.
It may be related to the speed at which I create and execute nodes? I do it very fast.
Hey @treyr, how is your docker configured? Is it using docker-compose? Iâm seeing this exact same issue on my production instance of N8N that uses docker compose and postgresql/traefik. But a local test server I just deployed using just straight docker/sqlite doesnât encounter this issue using the exact same workflow. Might be worth while comparing environments to see if there is something in the configuration that can be duplicated to introduce the issue.
@cleveradmin I pretty much use the default docker instance with docker-compose.yml and sqlite on a brand new droplet
All current apt patches, docker and n8n versions.
This has been and continues to be a problem for me with every update from every browser.
Maybe a local vs internet issue - can you copy the local to an internet host?
