Wait node items total counting more and more

[freek]

Hi there!

I just starting using n8n and I love it such a great tool! So I build a workflow that uses a wait for 3 days and in the executions I see the workflow now waiting. It has 1 input item nothing strange there only the output of the wait is on 84 and counting. Everything I refresh the items get a bit more and more. Am I using the wait node for something wrong? Or is this normal behaviour.

Running the 1.45.1 version on a ubuntu docker vps using the default database.

[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:

[barn4k]

hello @freek

That one could be a UI issue (don’t remember why it happened though)

[freek]

So the wait node waited for a few days but now the time is there but it’s not doing anything.

[barn4k]

Can you show the screen of the whole execution? I’m interested in why the Wait node has 1600+ items

[freek]

@barn4k

[BramKn]

Not sure what is going wrong here. The wait with the 1600 runs of it is probably a visual bug. But is not important for your issue I guess. As you simply want it to run.

I don’t know what the issue with wait node would be. But I have seen more topics on it.
To be honest I think you should never do it like this, as it is very risky having your flow wait for 3 days.
Better would be to write the record to a database. (Airtable/baserow/googlesheet) With a timestamp of when it can continue. And then have a flow check that table to see if it can start something for you and delete it from the list for example.

This way you will have more control and no waiting workflows.

[freek]

So on the webhook create a record in a table with a datetime and the body payload and a webhook node id then create a workflow that checks every minute/hour/day if there are records in the table, if so trigger the workflow node with the id from the database and pass the payload as body?

[BramKn]

Basically you just split the workflow into 2 parts. One sending to a DB or whatever and one checking at an interval if a record needs to run and then run it.

[freek]

Yeah I think that I’m saying that only the second workflow needs to have details so I think the payload needs to be stored in the DB and maybe a generic workflow can check on interval only that needs to to know what workflow to start.