Production issue interview question

1.list out the steps followed if there is any issue occurs in production while robot in orchestrator is running

  1. There are 4 transaction taking place , in which 2 is successful and the other 2 is also successful but the status is inprogress state . what can be the reason for this ?
1 Like

This is because of failure to update the status in the queue. Reason can be many. But we need to investigate the root cause.

  1. Review Orchestrator Logs to identify any errors or application issues.
  2. It might happen transaction is stuck or killed by manual intervention.
  3. Any message box or manual click is needed to finish the transaction.

Let’s go one by one

For this

  1. Check the Orchestrator logs.

The Orchestrator logs contain detailed information about the execution of all robots and jobs. You can use the Orchestrator logs to identify the specific error that is causing the issue.

  1. Check the robot logs.

The robot logs also contain detailed information about the execution of the robot. You can use the robot logs to get more information about the error that is causing the issue.

  1. Check the UI element that the robot is interacting with.

If the robot is unable to interact with a UI element, this can cause the robot to fail. You can use the UiPath Explorer tool to inspect the UI element and make sure that it is visible and accessible.

  1. Check the robot settings.

Make sure that the robot settings are correct. For example, make sure that the robot is connected to the correct Orchestrator server and that the robot has the correct permissions.

  1. Contact UiPath support.

If you are unable to resolve the issue on your own, you can contact UiPath support for assistance.

For this

  • The transactions are taking longer than expected to complete.

This could be due to a number of factors, such as a high workload on the system or a network issue.

  • There is a problem with the robot or the process.

If the robot is unable to complete a transaction successfully, the transaction will remain in progress state.

  • There is a problem with the Orchestrator server.

If the Orchestrator server is unavailable or there is a problem with the Orchestrator database, this can cause transactions to remain in progress state.

To troubleshoot this issue, you can follow the steps outlined above. You can also try to restart the robot and the Orchestrator server. If the issue persists, you can contact UiPath support for assistance.

Here are some additional tips for troubleshooting issues in production:

  • Have a rollback plan in place.

If something goes wrong in production, it is important to have a plan in place to rollback to a previous working state. This will help to minimize the impact of the issue on your business.

  • Monitor your robots and jobs closely.

It is important to monitor your robots and jobs closely to identify any potential issues early on. You can use the Orchestrator monitoring features to track the status of your robots and jobs and to receive alerts if any problems occur.

Hope this clarifies

Cheers @poojaskyrathore

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.