@Sarveswara ReddyI am not aware of a way to stop a work queue, however your bot can take itself offline and will accept no more work (until it is restarted). To do this, use the ReadyForRobotWork property of any application (Adapter). Unless every one of the applications in the project has this value set to True, Robot Manager will not send work to that bot. There is a corresponding property called ReasonAdapterNotReady that allows you to provide a message visible in Robot Manager. You can use this for startup as well. I typically set this to False by default and then after the project loads and I log all of the required applications in, I update this value to be true. In your case, you would detect some specific error or other condition, and then set this value to false.

@Sarveswara Reddy , I understand your request, but how would you start the work queue again? do you expect this to be manually or done by the same or another robot?

Instead of stopping/starting the work queue, I think your scenario would be better handled through case management. The robotic assignment provides extension points that you can leverage to automatically handle these scenarios.

You can specialise pyRepairAutomation or pyRouteAutomationToConflict to understand the outcome of your automation when the application to automate is down. Park the assignment for the time considered enough for the application to be again available and automatically move the assignment back to the queue for the same or another robot to process.

This solution allows you to automatically re-queue the required cases, use the robots to process other assignments if required, and to don't have to control manually or with more complex solutions when the application is back online to turn the work queue back to started.