I have this workflow:
- Receive stripe trigger
- Check if it’s 8am or later
- If true, send email
- If false, wait an hour, and then loop back and see if it’s 8am or later yet
Goal: Trigger a dunning email to the customer, but as Stripe triggers can come in at midnight, I don’t want to send emails until a sensible hour.
This seems like not necessarily the best way to wait until 8am (I could just do a
Wait until Current Time => calculate 8am today) but I thought ^^ would still do the job.
When an execution is triggered, the execution log shows it as continually
status = running whilst it’s actually waiting.
I would have expected it to switch the
status = waiting, especially as the wait is > 65 seconds so it gets passed off to the database for later execution.
Seeing it as
running for minutes, hours, makes me concerned that it’s going to result in a fairly decent server load, and also, just doesn’t seem right. I had two executions of this fail overnight (but can’t see why, hence the concern).
- Why isn’t it showing as
waitingin the execution list?
- Is it actually a problem/something to worry about?
- Is it worth rebuilding the time check to compare current time with 8am today (rather than a wait +1 hour, try again, loop)?
Running in n8n cloud.
(i’ve removed the nodes that follow TRUE from
IF wait until 8am for clarity)