Schedule run creating duplicate runs at midnight

Questions
1

Looks like this has been discussed a few times but without a really clear resolution. I just had a schedule trigger run twice last night, and I’m hoping I can figure out why that happened instead of making everything idempotent.

Looking at the json the interval is null if you leave it at default settings (midnight daily run). If I set the hour/minute it seems to only run once, but setting it explicitly to midnight clears out the interval to be null again.

Not sure if I’ve identified the issue or if it’s just sporadic, but it’s odd to me to have that nulled out if my settings happen to be the default ones (of course, only matters if the null interval is causing problems).

2

Hi there, @Gentry_Davies , have you tried updating your n8n instance?

Moreover i would also suggest for you to use custom cron for the schedule trigger, i find that more reliable

3

Appreciate it, will try both. Wondered if custom cron would be a better choice.

4

Sure thing men, lemme know if it helped, and if it does please click the solution button as it would greatly help me

Previously i also suggest this to approach where theres an issue with the schedule trigger, and for him, it solves the problem, and if you want to know more about it, ill reference it here

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.