Execution preview didnt update when Webhook timer node confirm. But, Actually, the process status has been updated to "wait/succeed/failed"

Questions
1

Describe the problem/error/question

When there is a manual confirmation node with a Webhook timer, clicking on confirm will change the execution status of the workflow to “running” and the page will also show “running”. However, the page status does not update further and continues to show “running”, while the actual workflow status has already been updated (waiting/failed/successful).

What is the error message (if any)?

none

Please share your workflow

image
image1620×565 114 KB

when

Information on your n8n setup

  • n8n version: 1.24.1
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm
  • Operating system: mac os
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hi @chris-deng :wave: Thanks for sharing your setup details with us, too!

Are you by any chance using a reverse proxy to access n8n, or are you accessing the IP directly?

4

The local service is started with “pnpm run dev” ， be accessed through 127.0.0.1:8080.

5

image
image817×692 110 KB

It should be missing the condition check for stoppedAt === null in this existingStillRunning condition.

6

Hi @chris-deng - can you try using the latest version and seeing if the issue still persists? It would also be handy to have an example workflow where this happens.

7

The latest version of the code is still in use, and during the execution process, there are multiple manually confirmed execution nodes. After confirmation, the status remains as “waiting” and the canvas is not updated until the end when it shows “success”. However, after manually refreshing the page, the canvas displays the completion of the execution.

8

Hi @chris-deng :wave: Can you try using port 5678 instead? That might give better results.

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.