Failed jobs in Orchestrator

Help Orchestrator
1

Hi everyone,

I wanted to understand how you usually handle failed jobs in Orchestrator in a production environment.

Do you prefer using automatic retries, queue retries, or a combination of both? Also, what’s the best way to monitor repeated failures and troubleshoot them?

Would appreciate any suggestions or best practices from your experience. Thanks!

2

Hi @Mayuresh_Chavan3 ,
Retry temporary technical failures, handle business failures separately, and use meaningful logging to troubleshoot recurring issues.

Thanks

3

Hii @Mayuresh_Chavan3

From my experience, I prefer using a combination depending on the scenario.

For temporary issues like network/API timeouts, automatic retries can be useful. For queue-based processes, I usually rely on queue retry settings so the failed transaction can be retried independently.

For repeated failures, I would check the job logs and exception details first, identify whether the issue is application, data, or infrastructure related, and then decide whether a retry is appropriate.

I’d also avoid blindly retrying every failure, especially for business-rule or data-related exceptions.

4

Hi @Mayuresh_Chavan3,

I would suggest handling as many exceptions as possible at the workflow level before relying on Queue Retry / Transaction Retry.

For example, if a particular workflow is calling an application and gets an error, retry that specific workflow. There is no need to retry the entire transaction if the issue can be handled at the workflow level.

Use Queue Retry when the failure cannot be handled at the workflow level or when retrying the complete transaction makes sense.

Avoid retrying Business Exceptions. However, if the data can be automatically corrected, you can postpone the transaction and process it again in the future after the correction.

For production monitoring, configure Orchestrator alerts and notifications for critical or repeated failures. Use structured logs to capture the process, transaction, exception type, and relevant details. You can also use UiPath Insights for dashboards, historical analysis, and custom alerts to identify recurring failure patterns.

Thanks!