Wait node "At Specified Time" not working correctly

[lyfterteam]

I’ve been trying to setup my follow-ups in N8N and it’s been hell…

First this bug (which hasn’t been solved yet and hasn’t gotten any answers from any mod).

And now, I find that when I use the “At Specified Time” hard-coded option on the Wait Node, it doesn’t work either.

According to a moderator on this other post, the date should be pased in ISO format: so I passed it in ISO format.

Not working either… That run from the screenshot started at 17:00

Had to continue running at 19:03

At the time of posting this, its 23:26 and the node just kept waiting infinitely.

Share the output returned by the last node

No output, just infinite wait that breaks all my logic…

Information on your n8n setup

• n8n version: 0.214.1
• Database you’re using (default: SQLite): SQLite
• Running n8n with the execution process [own(default), main]: ?
• Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker

[mohamed3nan]

Hi @lyfterteam,

Try removing the milliseconds and the Z timezone marker at the end. For reference, something like this:

{{ new Date($now).toISOString().slice(0,19) }}

[lyfterteam]

Not working either.

The following workflow proves that the Wait node is indeed broken:

It’s supposed to continue 10 seconds after the workflow is ran. It never does

[mohamed3nan]

I think the issue is with toISOString() (it always prints UTC)

can you try remove it and use .toFormat("yyyy-MM-dd'T'HH:mm:ss") instead

this example works on my end…

[lyfterteam]

I posted a bug for this on GitHub: Wait Node "At Specified Time" is completely broken · Issue #14723 · n8n-io/n8n · GitHub

Temporary solution:

Use the “After Time Interval” Resume value and calculate the minutes between the current time and your desired run time:

{{ (.getTime() - new Date().getTime()) / 60000 }}

• /600000 for hours
• /60000 for minutes
• /6000 for seconds

Workflow showing it:

[mohamed3nan]

@lyfterteam Did you try this:

Wait node "At Specified Time" not working correctly

I think the issue is with toISOString() (it always prints UTC) can you try remove it and use .toFormat("yyyy-MM-dd'T'HH:mm:ss") instead this example works on my end…

[lyfterteam]

Sorry, I replied before I saw this.

Looks like this works!

However, I think they do need to update the documentation, or maybe make it error out of the time is “unreachable”. The ux is terrible for this node

Thank you very much!

[mohamed3nan]

You’re welcome!

If it helped, could you please mark the post as the solution?