I upgraded to 3.9 last night and since then I’m battling to get scripts to start on start-up. They eventually go through after the first interval period, but no on startup.
I’ve attached some graphics.
Any pointers please?
I’ve deleted the scripts then recreated (via copy and paste) and I’ve even deleted and recreated the schedules but to no avail.
ok I added a ‘:delay 1m’ to the start of the script which DOES delay the running of the script by one minute. I then rebooted the box but alas the script did not run until the first interval period was over. So in other words it didn’t even run after one minute’s delay.
I havent upgraded scripts to 3.9 yet but will test our ddns one. It might be that the script isn’t liked ?
Also, you can change the scheduler from startup to 00:00, if its interval is every 5 mins then it should just run every 5 mins, as long as its after midnight ?
Ok I asked support what was causing this and they said “If scheduler have both interval and start-time=startup set then script will not be executed at startup. It was made to work that way.”.
So what I’ve done is create two scheduler items for the DDNS, once to run on start-up and then another for the interval period count.