Hi, I am facing a serious in orchestrator. I have scheduled a bot exact at 12:25 AM but if you see it directly shows me the strange time here. 2, 3 5 how it’s skipping the time.
Because of this, my other process skipped as the situation became deadlock.
Please suggest, why the time fluctuates, this process hardly takes 1 hour after this second process started at 2 AM. But this first process showing me the time indifference. The rest process got canceled automatically.
Yes, Bro I have checked already. Sometime it’s gives me improper timing.
last week it gave me date of starting on 31 Dec and Ending in 30th. So this is strange.
Note - Timezone is correct. If this is working for the last days, now it;s giving me the wrong timing. But how it can show me start from 12:10 am then direct show me the timing 2 am, 3am 5 and 6am, it shows me completed in 7am. Others process got affected due to this. It’s not giving me always this timing but sometime it’s giving me this execution timing. but if sometimes giving me this so other process get cancelled automatically.
It depends bro. Generally first which is start at 12:10 am takes 2-3 hours. So that’s way I gave the gap. But If you the timing of execution for only first process which start at 12:10 is something ambiguous. The rest process not taking much time to execute.
see how it’s showing the timing.
Hi,
Have you fixed it? We are also experiencing this now, our scheduled triggers are all delayed by 1 hr (if job should start at 9am , the job will run in our machine at 9:50 or 10:00++am, everything was checked timezone in the orchestrator, triggers settings, local machine time/date. Everything is the same.
I can’t say its connection issue since when i start a job manually in the orchestrator, it will send a command automatically to the machine.