Why does my robot start slowly when using the AllProjectsStarted event?
When using an AllProjectsStarted event to start automations, the robot’s status as displayed in Robot Manager can make it seem that the robot is stuck “starting” until the automations complete.
When an unattended robot starts automations using a synchronous link emanating from an AllProjectsStarted event, there is a step in the registration process that is not completed until the automations triggered by the AllProjectsStarted event are completed.
The best practice is to use synchronous links to kick off automations from the AllProjectsStarted event. This method allows the system to make sure that applications are started, logged in, or navigated properly before beginning work assignments.
Using synchronous links
If you use synchronous links to start automations from an AllProjectsStarted event, if those automations take a long time to complete, then the robot’s status in Robot Manager can display as below. This is your indication that the system is finishing the automations.
If the runtime startup sequence, which includes the AllProjectsStarted automations, exceeds the default package load time of 60 seconds, you can lengthen it on the work group screen (package widget) here:
If the default package load time is exceeded, then you see this message on the audit log for the robot. Once the AllProjectsStarted automations complete, the robot registers successfully.
Using asynchronous links
While it is possible to use asynchronous links to start automations from an AllProjectsStarted event, this is not the recommended method. If you follow this method, then once that asynchronous link is passed within the automation execution flow, the AllProjectsStarted event is considered complete, the Activate command is sent to Robot Manager, and the heartbeating begins.
Using asynchronous links to start automations from an AllProjectsStarted event allows the robot to finish the registration process sooner. However, there is no validation that all applications are started, logged in, or navigated properly before the Activate command is sent and heartbeating begins.