Got a strange behavior today, … In a small loop (10 items), the browserflow node (isnotconnected) kept running at item 9 (at list visualy) without blocking the workflow (the next node was executed while the browserflow node was still running, …
In the screencapture, you can see 2 different nodes runing in the same time (browserflow and wait), … Also, 1 item was missing , … you see 9 items have been processed
So, the workflow finished, showing 9 items processed while the log showed 10 items processed at the end
What is the error message (if any)?
No errors, logs, … just this visual bug, very confusing. Also, the difference between the editor statistic/log and the execution statistic/log
Hello hsteph, i’ll trying to help you from the problem yaa!
The “two nodes running at the sametime” you saw isn’t your logic being wrong, but its the UI live update stream dropping mid-loop. Thats why the execution log processed 10 items, and the editor canvas show only 9 items, and sometimes two nodes as “active“ at once.
Maybe there are some point it might be happens:
n8n backend continues fine, but the canvas freezes one step behind
By the time you check Executions, everything is correct, but the live view is misleading.
There are several suggestion that i can give you to try:
Verify the Executions tab, trust that over the live view when you’re in loops with Browserflow.
Increase WebSocket/read timeouts (e.g. Nginx: proxy_read_timeout 3600; proxy_send_timeout 3600; proxy_buffering off;). For Traefik/Coolify, set forwardingTimeouts higher and make sure upgrade headers are passed.
Try to access http://SERVER:5678 directly (no proxy). If the bug disappears, its 100% the proxy/WebSocket handling.
I see your n8n version is 1.109.2, maybe there were multiple UI and execution status fixes after that. You can try to update to 1.112.4 for the latest and stable version n8n.
Maybe thats all i can share the solution for you, i hope your problem can be solved.
