On n8n cloud, I have a workflow where the Schedule Trigger is set to Trigger Interval: “Hours”, Hours Between Triggers: “8”, Trigger at Minute: “45”.
This execution has not triggered in 5 days now. What would cause this to happen? How do I debug if workflow is not even starting? Is scheduling reliable on n8n cloud? This node never triggered after changing it to 8 hour interval, up from 4 hours.
Workflow is active/published, I am on Starter (Annual) Plan, we are not over execution limits. Instance has not been rebooting that I can tell (how to see uptime?), other executions that are more frequent, or less frequent, have been running.
I noticed the problem under a previous n8n version, so I updated it to 2.6.4 (Latest Stable), which restarted the instance. This workflow still has not triggered at all, so clearly there is some kind of problem. How to investigate? Are there logs? I can’t see anything relevant on n8n cloud settings. The node version says “Schedule Trigger node version 1.3 (Latest)”. I don’t see anything in Known Issues in the forum about schedule triggers entirely failing to run? Don’t know where else to check for a problem like this.
Hi @danimal Welcome! I recommend toggling the configurations of that trigger and make sure to publish your workflows every time you make any change, also you can see common issues and node description here:
Hey Just a sanity check here, From my exp. using cron jobs are more reliable instead selecting the time in the schedule trigger. Can you try using a Cron job once and let me know if still errors or doesnt run for you.
Ok thanks for the suggestions. First I re-published it using Hours Between Triggers: 2, and it started executing again.
I changed it back to 8 hours, re-published, and it again failed to execute. I will try the cron method now, hopefully that will work.
So it sounds like there are bugs where the Schedule Trigger fails under unknown conditions, and no way to debug it? And there is no way to contact n8n cloud support to investigate a bug either, short of paying for an Enterprise subscription?
I had thought n8n could execute reliably, but I guess all workflows need external monitoring to ensure they run, that’s pretty unfortunate.
Hey @danimal I know it’s a bit frustrating you can contact the support for flagging this situation and for long term use i recommend you to use the self hosted version as it is cheaper and more reliable.
The cron job is a ncie method to deal with schedule triggers as ionly use cron jobs whenever I’m operating on schedule triggers, Also can i ask you to mark the reply as a solution, if your problem has been solved or if you are satisfied with the current reply or help.
Also n8n offers email support through the [email protected] , You can flag this to them as well about the issue.
