Job does not start as scheduled, stops, no logs

orchestrator
schedule

#1

Job scheduled for 00:00 AM – 7:30AM, fails to kick off on right time.
No entries in the logs.
What are the possibilities for this case?
Any other logs that could give us a clue?
See attached screenshots.


#2

Hi @cchilumula

Please do see the below post for your reference

Thanks
Ashwin S


#3

We have the stop defined.
The job triggers after stop time and moves to stop state.

2


#4

We also have should stop inside the package.
The same package & version worked before.


#5

HI Ashwin,

Please notice the job did not kick off on time. Another bot with on same schedule is not tested to work fine. The thread “scheduled job in orchestrator doesn’t stop” is not relevant to our issue.

What are the possibilities of a schedule failing to kick off the job? Where do we find the error?


#6

Hi @cchilumula, are you able to check the detailed log from your job. Orchestrator Job page > View logs.


#7

Job log is empty. It is on production and trace not enabled.


#8

Any updates on this?