UiPath Queue Retry Practice: Queue Item Statuses and Retries

Free UiPath queue retry practice for the ADAv1 and ADPv1 exams. Each problem gives an Orchestrator queue's Auto Retry setting and what each try of one transaction runs into: tap the status each queue item ends with, then give the retries and attempts. A wrong answer names the slip, such as retrying a business exception.

   
   
   

  1. Try 1 
  2. Try 2 
  3. Try 3 
  4. Try 4 
  5. Try 5 

Status each queue item ends with

12345

Answer to see the working.

UiPath ADAv1 and ADPv1 prep

The ADPv1 exam description lists "Build a REFramework project with Orchestrator queues." and the ADAv1 one lists Queues among the Orchestrator folder entities you use. Start with the free real exam questions, then get the full pack.

UiPath ADAv1 Associate
196 real exam questionsUS$39
Free: 24 questionsGet the full pack
UiPath ADPv1 Professional
320 real exam questionsUS$39
Free: 38 questionsGet the full pack

Queue retry FAQ

The queue retry rules in short
  • Application exception and Auto Retry on: the item ends Retried and a new queue item starts as New.
  • Max # of retries: how many times a queue item is retried. With all of them used, the next application exception ends Failed.
  • Business exception: not retried by default, the item ends Failed.
  • Auto Retry off: nothing is retried. Turning it on later does not retry items that already failed.
  • Postponed: the same item goes back to New. It is not a retry.
  • In Progress about 24 hours without being processed: Abandoned.
  • Deleted on the Transactions page: it can no longer be processed.
  • REFramework with Orchestrator queues: MaxRetryNumber in Config.xlsx must be 0.
What is the difference between a business exception and an application exception in UiPath?

An application exception is a technical issue, such as an application that is not responding, and a retry may solve it. A business exception means data the automation depends on is incomplete or missing, such as a phone number missing a digit, so a retry does not help. With Auto Retry on, Orchestrator retries a queue item failed with an application exception. By default it does not retry business exceptions.

What does Max # of retries mean on an Orchestrator queue?

It is the number of times you want a queue item to be retried, from 1 to 50. The field shows only when Auto Retry is selected. Without Auto Retry no transaction is retried. So with Max # of retries 3 and an application exception every time, the item is retried 3 times and tried 4 times in all.

What status does a retried queue item end with?

Retried: the item failed with an application exception and was retried. The retry is another queue item added to the same queue, and it starts as New. Each queue item points, through its Key field, to the original queue item of the retry chain.

What should MaxRetryNumber be in REFramework when I use Orchestrator queues?

The REFramework Config.xlsx says MaxRetryNumber "Must be 0 if working with Orchestrator queues. If > 0, the robot will retry the same transaction which failed with application exception." With a queue, the retrying is left to the queue's Auto Retry. Every problem in this drill uses MaxRetryNumber 0.

When does a queue item become Abandoned?

When it stays In Progress for a long time, about 24 hours, without being processed. The statuses diagram adds that items processed by a long running workflow are not abandoned after 24 hours if the job running the item stays Suspended.

Is a postponed queue item a retry?

No. Postpone Transaction Item puts the same item back to New, and a robot takes it In Progress again. No new queue item is added, so it uses none of the Max # of retries. The try after a postpone is still an attempt.

Does turning Auto Retry on retry items that already failed?

No. Existing failed transactions are not retried. Only the transactions that fail after you set the new value are retried.

Do manual retries count toward Max # of retries?

No. Manual retries are not counted towards the maximum number of retries. Marking an item for retry by hand creates a new queue item with the New status.

Can a deleted queue item still be processed?

No. A Deleted item was selected on the Transactions page and marked as deleted, and an item with this status can no longer be processed.

What does REFramework call an application exception?

Its Config.xlsx logs one as "System exception." The REFramework documentation says that if an application exception occurs, the current transaction can be retried, and if a business rule exception is thrown, the transaction is skipped.

Which UiPath version does this drill follow?

The Orchestrator 2025.10 user guide. The ADAv1 and ADPv1 exam descriptions say both exams cover UiPath product versions 2024.10 and later. The Automation Cloud guide now shows Auto Retry as two options, Failed items and Abandoned items.

Sources
  • UiPath Orchestrator user guide 2025.10: Queue Item Statuses: New, In Progress, Failed, Successful, Abandoned (about 24 hours), Retried and Deleted, and the statuses diagram (postpone back to New, a retry as another queue item, the auto-retry conditions).
  • UiPath Orchestrator user guide 2025.10: Business Exception Vs Application Exception: an application exception is retried when Auto Retry is set; business exceptions are not retried by default.
  • UiPath Orchestrator user guide 2025.10: Managing Queues in Orchestrator: Auto Retry, Max # of retries (1 to 50), existing failed transactions not retried, manual retries not counted.
  • UiPath Orchestrator user guide, Automation Cloud: Managing Queues in Orchestrator: Auto Retry as Failed items and Abandoned items.
  • UiPath ReFrameWork repository: Data/Config.xlsx (MaxRetryNumber must be 0 with Orchestrator queues; "System exception." log message) and REFramework documentation.pdf (application exceptions retried, business rule exceptions skipped).
  • UiPath certification exam descriptions: Automation Developer Associate (ADAv1) and Automation Developer Professional (ADPv1): Orchestrator queues, REFramework with Orchestrator queues, product versions 2024.10 and later.
  • Checked 20 November 2026. The tool's own approach: every queue and try is invented; MaxRetryNumber is always 0, because the outcome with both MaxRetryNumber and the queue retry above 0 is not in the docs; an abandoned item only appears on a queue with Auto Retry off, because the 2025.10 pages do not say whether one is retried automatically; anything else the pages do not state is left out. An independent re-solver agreed with the drill on 24,000 generated problems.

Checked 20 November 2026 against the UiPath Orchestrator 2025.10 user guide, the UiPath REFramework repository and the UiPath exam descriptions.

More free tools

All free tools