Wait node doesn't work for more than 1 minute

[VinceRocher]

Hi, I am facing what seems to be a bug with the Wait node: when I wait for 1 minute, it works fine, but when I change the duration the node doesn’t wait, and at the same time keeps being on “Waiting” status in the execution logs. How should I do to resolve this?

[n8n]

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:

[Jon]

Hey @VinceRocher,

Any time over 63 seconds I think it is will move the wait to the database to be resumed when it needs to be. This means if you are testing a worklfow from the UI and you add a 2 minute wait you will just see it in the execution log until the wait time is completed.

If you are seeing wait nodes lasting longer than they should in the execution log it could be that you don’t have the default timezone or the TZ environment option set correctly. If you are using Cloud we would need to dig into it a bit more.

[VinceRocher]

Hi Jon, thanks for your swift reply.

Yes, all the workflows last way longer (they even do not end at all, their status is “waiting”). I am using Cloud.

[Jon]

Hey @VinceRocher,

Can you send in an email to [email protected] and we can take a proper look at your instance and see if we can work out what is going on. If you can include an example workflow with the issue as well that would be handy.

[VinceRocher]

I will, thanks!

[mariana-na]

Hi @VinceRocher ,

Just sharing the answer here as well in case other users come across the same issue

There seems to no inherent issue with the node, but there are some UX specificities that can indeed create confusion.

When a wait node runs for up to 64 seconds, the UI displays the running node and proceeds after the wait. But, from 65 seconds onwards, the wait is offloaded to the database, meaning that the UI won’t display the same way, and the execution result is shown in the execution log screen. Wait | n8n Docs

So, when you see this and receive that bottom warning, it means that the execution is waiting, and that its result should be viewed in the Executions screen.

Once in the execution screen you can see that the execution (which I started at 9h30 and set to wait for 1.5minutes) has indeed finished. Here you will also be able to open the nodes that come after the wait node and see that they have run and outputted data.