I’m not sure why. I have been using N8N since 2020 and don’t remember seeing it live. May be cost of rendering it live is too much? Maybe? This is something the n8n team can answer correctly.
non-manual executions don’t have access to the Websocket/SSE connection, which means the execution engine can’t push updates to the frontend.
To be able to push execution updates is also the main reason why manual executions don’t run on workers in queue-mode.
We hope to address this some day, but we unfortunately also have quite a big list of tasks to address first .
Additionally, there are some execution processes, when clicking on execute on the process definition page, if the execution takes a long time, such as when there is a wait (webhook call) node in the middle, the execution page canvas will stay at wait.
Even if the final process is successful, the canvas will not be updated unless the page is manually refreshed.
@chris-deng instead of adding new questions to an existing topic that are only tangentially related, please open a new topic. This makes it easier for everyone to notice your topic + will help our support team with the organization of their work too.
There is no mechanism to let a user trigger a canvas update.
Manual executions update the canvas via a websocket connection, and since live executions do not have access to websockets (as pointed out earlier), unless someone rewrites the execution engine, there is no way to get executions updates from the execution engine into the frontend.
.
