Why retry is not working in system Exception in Reframework in uipath?

Help Activities
, , , , , ,
1

Hello everyone !
I am using Reframe work in my automation but the problem is, it’s not retrying the transaction item which got system exception and its moving to next transaction item.

What may be the problem ?

(I already provided MaxRetryNumber = 4)

2

@Prabin_Chand

Are u using queue or non-queue reframework?

3

@Prabin_Chand

For queue based processes retry must be provided in the queue auto retry field…

For non queue based it needs to be provided in the config file constants page

Please verify

Cheers

4

using DataRow

5

i am using datarow

6

@Prabin_Chand

Can you show how you configured…and did you remove any conditions in original re ?

Cheers

7

I have configured it in my client desktop.

But I am 100% sure that I have mentioned MaxRetryNumber = 4 in Constant sheet

8

In set transaction status workflow, does any error occured , could u check that ?

Also confirm the in_TransactionItem in set transaction status workflow is datarow or not ?

9

There’s no Error.
WorkFlow is running all well but only problem is when it get System Exception, it is not trying the same transaction item but its taking new transaction to process.

10

As @Anil_G mentioned, did u changed any condition in Reframework?

11

Nope.

(Confirmed : in_TransactionItem set to DataRow)

12

Last thing, is it possible to share screenshot of logs when error occurs ?

13

Check in Main Workflow in variables pane if RetryNumber = 0

14

yes, it is set to 0

15

I can’t,
it is in client desktop and i cannot copy anything

16

If you run this process from orchestrator, check in trigger if input argument this value was provided

17

i didn’t get it

18

@Prabin_Chand

Follow the steps…

  1. put a break point at system exception and run in debug
  2. Now use step into and go till the execution goes till retry transaction number and continuously check the maxretrynumber from config file and also if the condition is being executed properly in the retrytransaction.xaml

cheers

19

Sorry, my bad.

As @Anil_G said, running in debug it is a good way to find out whats happenning

1 Like