Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

UiPath Pitfall #3: Expecting Orchestrator to Retry a Business Exception

说明与用途

在 UiPath ReFramework 中,错误的异常分类导致队列重试行为不正确。通过区分 BusinessRuleException 和 ApplicationException,可以控制重试并提高错误透明度。

问题

Queue items fail without retry or are retried unnecessarily due to incorrect exception classification in UiPath Orchestrator.

结果

By distinguishing BusinessRuleException from other exceptions, queue items are retried only when a technical issue may resolve, preventing wasted runtime and improving failure transparency.

工作流

  • 1. In Process.xaml, validate input data early and throw BusinessRuleException for data issues.
  • 2. In SetTransactionStatus.xaml, set ErrorType to Business for BusinessRuleException, Application for others.
  • 3. Configure Orchestrator queue with Auto Retry enabled and set MaxRetryNumber to 0 in REFramework config.
  • 4. Use Retry Scope for flaky steps that need immediate retry without failing the whole item.
  • 5. Handle shared login failures in Init state and stop the job if necessary.

证据

Application exception + Auto Retry turned on for the queue: Orchestrator retries the item, up to the queue's max number of retries.

来源

Business exception: Orchestrator doesn't retry it by default.

来源

In REFramework, what you throw is the decision.

来源

Ask one question before throwing: would running this exact item again, unchanged, have a real chance of working? Yes means Application. No means BusinessRuleException.

来源

  • 记录日期: 2026-11-01T02:59:08.015Z