Orchestrator error - #schedule for #process could not start. The stream has been closed

orchestrator

#1

Hi,

My bot is running with Orchestrator since 2 months. Yesterday, I got an error message mentioning '#schedule for #process could not start. The stream has been closed. ’
I cannot find anything related to this error anywhere. Also, it is not reproducible so I am not able to find the root cause.
Can anybody help?

Below is the screenshot of error:
imageimage.png874x329 8.2 KB
Regards
Jhalak


#2

Below is the screenshot of error:


#3

One problem could be

If you have specific robots option checked in the schedule, verify if at least one robot is selected to run the job.

Also, does the process run normally when started from the jobs?


#4

We are getting the same error notification(As jsriv1 mentioned) every day at the same time (2:01).

To Answer your question:
Yes! We have checked the specific robot in scheduled.
Yes! the job runs fine throughout the day.