Any Idea why the robots can't take a work? Moreover, RPA service generates a new operator and runtime also generates a new operator. However, only the operator that is created by the runtime becomes the robot. What do we do about the operator created by the RPA service?
If you have adapters in your solution, they have a property called "AdapterReadyForWork". This must be set to True for all adapters before they will start accepting work. Normally on Startup, you would login to each app and get them running before setting this property to True for each adapter. The operators created are done automatically, so you shouldn't need to do anything about them accept leave them be.
An adapter is the main part Pega Robotics. It is either the Windows Application, Web Application, or Universal Web Application (or Text Adapter) that you use to perform interrogation. If you do not have any, then I would assume that the robot would be ready for work on startup, although I will likely never be involved in a project without an adapter, so I cannot be certain that it works that way without being able to test it.
I do not have an environment available to test that. Have you configured your Robot correctly and you can see it is showing as green in your Robot Manager?
From your single screenshot alone, I cannot offer any specific suggestions. Make sure your activity name matches. Make sure that your Robot is registered and showing green in the work group within Robot Manager. Make sure that the case flow is placing the case in the work queue inside of the correct work group that the bot is assigned to.
That looks like everything is in order. What do you have the RobotActivity connected to? The ActivityStarted event should be connected to something in your automation as that is the trigger. When your automation is complete, it should call the SetCompletionStatus method.
You configure the workgroup from the CommonConfig or via the decision tables based on the registration user. At this point, I don't really have anything I can suggest without seeing your environment. I would suggest that you open a support request and get someone from support to look at your system. Please record the SR number with the post so that when it is resolved, we can update what was done.