N8n wait node not continuing after time interval

Hey there,

this workflow had been working well, but after I updated to the version 1.36.2 yesterday, the workflow has been stuck and never continued at the wait node of 15 minute.
I’ve tried to change the timezone to GMT, our timezone, but still doesn’t work. No error message occurred but the execution showed waiting and not yet finished since last night. Any thoughts on how to troubleshoot this?

Here’s the wait node:

Information on your n8n setup

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

Hey @Mei-Chen_Lee

Could you please share your workflow, that will let us help you easier. No worry about credentials they won’t be shared.

I’ve just tested on my instance and wait node work as expected, you have set wait for 15 minutes, is that what you want? Can you try different values just to check if that work for like 5 seconds?

@edit
BTW. I see on screenshot that execution is waiting. Maybe you meant 15 second? :thinking: From my POV it looks like wait node is still waiting
image

Thanks

Hello @Shirobachi

Thank you for the reply! The wait time is 15 min. As there’s a huge amount of data, that’s why we set the wait time a but longer.

Here’s part of the workflow:

instead of using wait node use function node and use the code below

const waitTimeSeconds = 300;

return new Promise((resolve) => {
  setTimeout(() => {
    resolve(items);
  }, waitTimeSeconds * 1000);
});
2 Likes

300 sec = 5 minutes

It doesn’t seem working. I change 300 to 600 and I’ve waited 20 min and it’s still in execution.

for how much time do you want to wait

I need to wait at least 10 min

weird, I think it should work, can you check from smaller value if it’s the same?

@Arsh_Tyagi @Shirobachi Thank you guys! I keep the waitTimeSeconds to be 300. And it’s working!

1 Like

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