Hello,

i have a scheduler that's running twice all the time and i have no idea why.

Start Time: 04:15:00
Interval: 1d 00:00:00
On Event:
interface disable tdsl-768
interface disable tdsl-1000
interface disable sdsl-768
interface enable tdsl-768
interface enable tdsl-1000
interface enable sdsl-768

So it just disable all dsl interfaces and then enable it again (to force a reconnect during night)

According to the logs the scheduler was running at 04:14:59 and again at 04:15:01 ... the "Run Count" increased twice and i absolutley have no idea why!

Any Hint?

It's a ROS 3.6

I don't mean to raise a thread from the dead but this bug still exists in all versions <=3.13, it affects most of our scheduled scripts across RB's, WRAP's and x86 systems running ROS alike, and as our ROS based network grows it is becoming a problem.

Does anyone have experience here with scheduler running twice seconds apart? is it possible a timezone setting or running NTP client be the cause?, perhaps a fix/workaround for this? any comments would be appreciated.

Just checked one of my scripts that was scheduled to run, no issues here.. running v3.11 on the router

Scripts are running twice only when interval is set to 24h.

....
Scheduler runs twice for no reason is true!

Scripts are running twice only when interval is set to 24h.

how to fix it?????

I have the same problem with the dual execution in the scheduler in my X86 Server.
I had this problem in the July / August 08 MT Support reported from there I got a reply the problem is known and we want it in the next version fixed.
Until now, it is unfortunately not yet been fixed Perhaps what is being yes in the V3.15

Hi all!

I have a similar problem too. Two scripts run twice. But not every day. From what I noticed, the issue occurs 24 hours later after task creation, then everything works fine until the week begins or something like this.
Taks start time is 11:56:00 and the interval is 1d 00:00:00.
CHR at x86. ROS stable verions 6.49.12 or 6.49.13 don't matter.
Task deletion and re-creation don't help.

Any ideas other than upgrading to ROS 7?

For those who are interested, the problem is solved by rebooting the host OS and guest OS (ROS). It is unknown which one caused the problem, since both were restarted on the same day.