Macro Scheduler not repeating schedule

[Marcus Tettmar]

Well, my two simultaneously scheduled macros with schedules set to ensure they ran at the same time have continued to run for several days. However, as expected, the logs show how certain steps in one were delayed by the other.

When a repeating macro misses a schedule the time should advance to whatever is the next slot. This is certainly what happens during startup checks but I'm now going to double check that this is also happening after each run so that e.g. a macro set to repeat every 10 mins which starts at 2pm but takes 15 mins should advance first to 2.20pm not to 2.10pm which has now passed.

Bear with me.

[kh_kevin]

thanks very much for looking into it. just to clarify, in my experience the next scheduled time works fine for me when the macro successfully completes. i think maybe when it hasn't scheduled the next time correctly (and screen stays unlocked), the macro just hasn't actually completely due to the other script. once the other script finishes, the next time is set correctly. havent confirmed this though.

it appears to me that the issue is script A gets stuck waiting for script B to finish before script A can finish (due to RunProgram?). thanks again!

[kh_kevin]

hello, does there happen to be an update on this issue? this problem is still occurring intermittently for us. thanks,

[Marcus Tettmar]

hello, does there happen to be an update on this issue? this problem is still occurring intermittently for us. thanks,

No, sorry, I forgot to update you. I did some more tests, testing multiple macros scheduled to repeat but run longer than their repeat interval, but the schedules all advance correctly. I've not been able to replicate a problem.

I wonder if it would be worth you sending us your dat files. While we wouldn't be able to run your macros we could replace them with simple macros which wait roughly the same length of time they currently take. That way we could replicate your sequence.

[kh_kevin]

Ah I see. If there is a script A and script B...well the issue now is that the script A schedule might not advance until script B has completed, rather than advancing when script A has finished. It does always advance if I wait long enough though. It seems to be some sort of threading issue maybe?? I've occasionally seen some C++ exit error that pops up but doesn't affect the script, so wonder if it's related or not.

Sure I can send the .dat file...where should I send it?

Thanks,

[Marcus Tettmar]

Please send to support AT mjtnet.com

If possible please indicate how long each scheduled macro usually runs for, as to replicate we'd need to replace the macro code with waits since they are unlikely to operate on our system.