Wait does not continue after scheduling

Questions
,
1

I have a problem scheduling my wait (when it is longer than 65 seconds)
As soon as I update or downgrade my Stack everything works as expected but, after a few hours, the flows do not continue after the wait, I have tried to look for a logic for the failure but without success.

I also noticed that when wait is not working, when I look at the logs in Docker, it does not update in real time, I need to exit and click on log again, when wait is working the logs appear alone at the same time. time that executions begin.

can anybody help me?

Captura de Tela 2023-09-11 às 12.26.40
Captura de Tela 2023-09-11 às 12.26.40797×534 33.2 KB

Information on your n8n setup

  • n8n version: 1.6.1 queue
  • Database (default: SQLite): postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • **Stack Docker: ** gist:6396b5599909b7abfd84ccfedf0b47c3 · GitHub
  • Operating system: debian 11
3

Hi @admdiegolima, I am very sorry you’re having trouble.

I tried reproducing this using n8n 1.6.1 in queue mode, but didn’t have any problems here.

Starting the workflow was working fine:

image
image932Ă—41 10.4 KB

It moves into the expected wait state after being triggered:

image
image1920Ă—895 33.7 KB

After the wait time, my worker picks up the execution as expected:

image
image745Ă—86 20.2 KB

…and the workflow moves into it’s final state:

image
image1920Ă—895 33.1 KB

Is there a chance you’re using n8n with an unstable network connection preventing your worker from picking up the job as it should? Are you also seeing this behaviour when not using queue mode (and instead have your main instance execute the jobs)?

1 Like
4

I believe it is not a case of instability in the connection, as I believe that this way it would only fail sometimes, and in this case, at some point all “wait” stops working, as you can see in the image below.

Captura de Tela 2023-09-12 às 11.49.48
Captura de Tela 2023-09-12 às 11.49.481070×998 139 KB

when I update or upgrade the n8n version and everything works perfectly for some time, for example yesterday I updated the n8n at 4:00 pm and it was working perfectly until today at 10:30 am, when they all stopped working.

Could you create an automation that generates several of these “waits” for the next 24 hours?

Could you share the stack you used in your installation?

In which database table and column is the data from a wait schedule saved?