Field note · found 11 November 2026
n8n Wait node with a date in the past continues immediately
When an n8n Wait node is given a date and time that has already passed, the run carries straight on, so a reminder timed as "appointment minus lead time" goes out at once whenever the appointment is closer than the lead time.
Test record: run by Fractional HQ on 11 November 2026 on self-hosted n8n 2.23.4, as replays of a real message. Runs 94159 and 94288 sent the reminder at once. Runs 94131, 94132 and 94136 paused and woke on time. Not tested: n8n Cloud, the Wait node's other modes, the length of the gap.
Symptom
On 11 November 2026 we ran our WhatsApp booking template on n8n 2.23.4 with reminders switched on. A customer booked 09:00 the next morning at a clinic on Paris time. The reminder lead time, which is how long before the appointment the reminder is sent, was set to 1,705 minutes. That is over 28 hours, and longer than the time left before the appointment. Meta accepted the confirmation, and the reminder went out straight behind it.
We saw the same thing later that day on the next version of the file. A booking for noon the next day, with the lead time set to 3,000 minutes, sent its reminder straight after the confirmation.
Why it happens
The template works out the reminder time by taking the lead time away from the start of the appointment, and it tells the Wait node to resume at that time. When that time was still ahead, the run paused and woke on the minute: three runs set for 12:33, 12:34 and 12:35 each woke at exactly that time. When the time was already behind, we saw no pause at all.
That is what we observed in those two runs. We did not read the Wait node's source to confirm how it treats a past date.
What we would change
We have not changed this in the template, so there is no fix here that we have run. The change we would make is an IF node before the wait that compares the reminder time with the current time and skips the reminder when it has already passed, because a reminder that lands a few seconds after the confirmation tells the customer nothing new.
Until then the practical answer is in the settings. The lead time has to be shorter than the shortest notice at which you take bookings, or some customers will get both messages together.
How we found it
Both cases are in our run log for that day. Run 94159 is the Paris booking with the 1,705 minute lead. Run 94288 is the noon booking with the 3,000 minute lead, made on version 1.1 of the file. Runs 94131, 94132 and 94136 are the three that paused and woke on time. All five were replays, which means runs we started from a real message sent from a phone, with the text changed.
What we did not establish
We did not measure how long the gap between the confirmation and the reminder was, only that the log records the reminder as sent at once. We ran this on one self-hosted version and not on n8n Cloud. We did not test the Wait node's other modes, such as waiting for a fixed interval or for a webhook call.
Written by Fractional HQ from its own runs. If your n8n behaves differently, email hello@fractionalhq.uk and we will correct the note.