I have built a robot in the Robotic Enterprise Framework, which runs smoothly locally. However, when I publish this to orchestrator and start a job with the unattended robot, some queue statusses are set to ‘failed’ and I don’t know why. Locally I can’t find a reason why these items are failing while the others are being processed succesfully.
When I look at the reason why it is set as failed in Orchestrator, it is being regarded as a business exception, which is strange, because I didn’t build the exception in the Framework. Some additional information, the workflow contains a switch function with four cases. Three of the cases seem to be processed succesfully while the items from the fourth case are being set as failed.
Please let me know if I can provide additional information, and thankyou in advance.
Hi @j.bude ,
Thanks for reaching out to UiPath community.
Implement detailed logging within your workflow, especially in the fourth case of your switch statement. Log relevant information, such as the input data, intermediate results, and any exceptions that occur.
Use the Log Message activity strategically to capture information about the flow of your process.
Thank you both for your answers, I added the log messages and was able to pinpoint down where the bot encountered the exception. Apparantly it was an issue with the UI element, but I figured it out and it seems to be working now!
You should always use many Log Messages throughout your automations for troubleshooting purposes. You can also turn on verbose logging for the robot, but I don’t recommend leaving it on all the time.