Scheduled trigger got delayed

Dear all,

Machine A and Machine B is having common user id.

A bot was scheduled to run at 8:00. But it got triggered late at 8:45.(Machine A)

Note: Another process was running in another machine which is having same user id. Process was ended at 11only(Machine B).

Still bot has started at 8:45 in Machine A.

Any reason for late trigger? please do suggest how to handle it?

Hi @lukas_krishnan ,

check the possibilities of timezone, time and mainly it got started late may be because Machine A was running some process. Check when was the previous run completed on this machine.

1 Like

the fact that it is the same user shouldn’t make any difference.
The question is whether some other process isn’t blocked machine A?

1 Like