Is anyone else having issues with a Scheduled Trigger node? I have 3 workflows using the Scheduled Trigger node, and every now and then when i make a change to one of the workflows and save it and activate, the scheduled triggers do not run. I have no idea why. I am running the latest stable version of n8n 1.93 cloud hosted. Please help.
Hello @hallbc welcome in the community!
When you save and re-activate a workflow with a scheduled trigger, n8n is supposed to re-register the cron job behind the scenes. Sometimes this doesn’t happen cleanly, especially if:
- workflow was modified quickly and re-saved without a full deactivation
- there’s a temporary sync issue between the UI and backend scheduler
So let’s try to:
- switch it OFF, wait 2–3 seconds, then switch it back ON
- add a Manual Trigger temporarily and run the workflow manually to make sure the logic still works as expected
if problems persist please share one of your workflows here
Cheers!
I was going to post a new message, but I am having the same issue, though my trigger is set for every 3 days kicking off at 9am. when I had the trigger for every 1 day the workflow worked. I de-activated the workflow, turned it off, made the change to every 3 days, saved and re-activated the workflow and it no longer triggers.
this workflow has been working since ~february and then just stopped working at the end of april.
any ideas?
1 Like
Hello @nixit,
- have any further changes been made to the flow?
- is n8n cloud or not?
- What version of n8n do you have?
Please tell me some other details
Happy to support you
thanx for responding quickly, and for the support, this issue is driving me crazy. 
-
no other changes to the flow have been made. after multiple days of not working (4-5), I de-activated the flow, waiting a few minutes and reactivated it and waited again. still would not run every 3 days. I copied the flow to a new workflow to test and that didn’t work either.
-
n8n community, running in a docker on an arch linux system that is powered on 24x7.
-
n8n version 1.94.1. the behavior has been the same on every version for the last 1.5 months.
Hello @nixit,
it’s really, really weird.
If you don’t mind me asking you more information, you’ve probably already taken these tests but it’s always better to ask:
- have you tried resetting the trigger once a day? That’s how it works?
- if a workaround (probably stupid) does not continue to work, it is to create multiple workflows that work on a different day of the week, I understand that it is not the same thing as the intended flow, but it could be a start
1 Like
hello @Gallo_AIA
thanx for responding. what do you mean by “resetting the trigger once a day?”
do you mean having the trigger be set to every day? if so, yes, I tried that and it started for 4 days in a row, so a daily trigger works.
I will test the multiple triggers on specific days of the week to see if that works.
on a side note, I set up a test trigger to run every 75 minutes, the trigger ran every hour on the hour instead of every 75 minutes.
maybe I’m not using the trigger starts correctly?
Ehy @nixit,
could you please share here some further info about the trigger?
here is the trigger:
first time posting a trigger, hopefully you can see it.
thanx for looking into it and offering insights.
The trigger seems ok, this is weird.
Please, try to have a separate workflows for different week day (maybe one every Monday and one every Thrusday).
I know it’s not best option but here we can get atm.
I will set this up and report back…
here is my current trigger:
Ok, let’s update on monday ok?
after I sent my last message where the trigger was set to start on saturday and tuesday, I changed it to saturday and monday. I am pleased to announce that the workflow did run on saturday and today, so this setting works.
I was thinking for my original trigger of running every 3 days. I can see how the system would get confused on when to run the trigger, since there is no start date for the workflow. having a “start date” on the daily trigger would be nice addition.
for now, I will just have the workflow run 3 days a week, instead of every 3 days. not completely ideal, but a good alternative.
thank you for your help.
1 Like
Mine is still not working. Here is my trigger node:
{
"nodes": [
{
"parameters": {
"rule": {
"interval": [
{
"field": "hours",
"hoursInterval": 7
}
]
}
},
"type": "n8n-nodes-base.scheduleTrigger",
"typeVersion": 1.2,
"position": [
-1440,
1100
],
"id": "22e19d24-5439-4d1a-8fa1-d502e644e72c",
"name": "Schedule Trigger"
}
],
"connections": {
"Schedule Trigger": {
"main": [
[]
]
}
},
"pinData": {},
"meta": {
"templateCredsSetupCompleted": true,
"instanceId": "ce34ab41a11f4e6d70d07d38073acd492c8491db32d17253876e76348fc76af3"
}
}```I took a look at your trigger node, which I could not just paste into n8n, it seems malformed?.?
a couple of questions…
- does my 2 hour trigger above work for you?
- I compared your node code to mine in a text editor and noticed that there is a difference in code, specifically the last bit:
“connections”: {
“Schedule Trigger”: {
“main”: [
]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “ce34ab41a11f4e6d70d07d38073acd492c8491db32d17253876e76348fc76af3”
}
}```
I changed it to this:
“connections”: {},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “ce34ab41a11f4e6d70d07d38073acd492c8491db32d17253876e76348fc76af3”
}
}
and I was able to import your node into n8n. not sure if that section I removed is causing anything.
I will report back tomorrow on the results of my test.
ps. my intention wasn’t to hijack your thread, but to add to it with my similar issue.
after testing your node for a day, I can say, it does and doesn’t work. when I created and started the every 7 hour flow (your’s that I copied, and one that I created brand new), they both ran twice, at 2pm and 9pm, but they never ran today. they should have run at 4am, but no dice.
it appears the every “x hours” or “x days” will work once or twice, but when the day changes it seems like the workflow execution time gets confused on when to execute further.
does this make sense to anyone?
cheers,
/nixit
the automations scheduled to start on specific days (mon, wed, fri) seem to work.
though the challenge seems to be when the automation is scheduled for “X number” of hours or days, the automation work on the day they are set up, but as soon as the day changes, it seems like the automation gets confused when to run next, though this is not always the case since a daily automation works, yet a every x days does not. an hour or every 2 hours seem to work, but anything more seems to stop work when the day changes.
any clues?
/nixit
Hello @nixit,
it almost seems like he doesn’t know what day it is as if it takes a variable {{$now}} to remind him.
I know this can’t be done but from what you say it seems to be so.
this makes sense. I will try changing my node to once per day and see if that fixes the issues, even though I would like it to run 3x per day, this will have to do I guess. I will report back.
what if you tried the suggestion @Gallo_AIA suggested, even though not idea, but copy the flow 3 times, and have each one run daily 7 (or 8) hours apart?
example,
flow 1 starts at midnight
flow 2 starts at 8am
flow 3 starts at 4pm
I know its not idea, but a workout for something that used to work.
/nixit