Usage of -Max # of retries -

Help Something Else
1

Hi All,

Could you please help what is the usage of’ Max # of retries’ while creating Queue in orchestrator and where it would be affected whether in Business or System exception.

image
image1169×581 44.2 KB

Thanks in advance,
Pavan.

2

Automatic retries are only done for application (system) exceptions. The max # of retries is exactly that, the maximum number of times a queue item will be retried before it is marked as fail.

3

Thanks for the response @postwick ,

Could you please provide solution for below queries as well.

  1. I am giving Max of retries=3, for first time it is throwing system exception and exactly in which .xaml it will take retry as 3.

  2. Does it move to other state when completion of first retry or it complete 3 retries and moves to next state ?

Thanks in advance
Pavan

4

we would recommend to check out the REF related courses available at UiPath Academy

5

The retry in the queue just means the queue item is marked as status Retried, and a New queue item is created. For example, if you have it set to max 3 retries, and they all fail, you’ll have three queue items marked as Retried, and one as Failed. If you look at the details of the queue items, on the history tab you’ll see this progression as the queue items are linked.

It has nothing to do with any XAML files. It just results in a new queue item that will then be processed by the automation.

1 Like
Forum Engagement Daily Reports
6

I have set Max of retry=3 while creating Queue in orchestrator and I have 100 queue items in New status.

First Queue item thrown System exception, now I have 101 Queue Items.
1- Retried
100- New

But as you explained in previous chat, I am not getting 3 retried queue items and 1 Failed item.

image
image1126×461 19.5 KB

7

@Pavan_kumar15

So this is how it happens with queue retry

  1. A queue item is fetch
  2. The queue item fetch is failed
  3. The status of queue item is set to failed by ref framework.
  4. Then in the backend the queue mechanism kicks in and check if the max retry number is reached…how do it know is that number is stored with queue item…you can check that also by chekcing transactionitem.retryno
  5. Now once the retry mechanism is kicked in…then status changes to retried and one more item with new status is added and norw the backend retry number for that item would be 1

Cheers

8

It doesn’t create 3 new items all at once when it fails. It creates a new item, then the automation tries to process it. If it fails again, it will be retried again and a new item created.