Hi all,
I have a queue with a Retry Count of 3. In my process, if a System Exception occurs, I want to add a row in my report indicating the failure.
The challenge is: if I add the Add Data Row activity inside the System Exception sequence without any condition, it will add the same row 3 times because of the retries.
What condition or approach should I use so that the status is added only once to the report, regardless of the retry attempts?
hi, @Rizwana_KM
i think that happens because the queue item is retried multiple times so your reporting step also repeats. you have to log the failure only when the transaction reaches its final attempt.
you can check the RetryNumber property of the TransactionItem
example: if TransactionItem.RetryNumber=TransactionItem.RetryMaxNumber
then Add Data Row to your report.
Hello @Rizwana_KM You can use a int type counter variable initialise it before the retry and then inside the retry you can use if condition with counter.equals(3) so in then block you can use add data row byt this is static so the number of time you’re retrying then that number you have to out in condition also you can log the error in retry activity and use add data row outside the retry activity so it will write the data only once after retrying the activity.
Cheers
I would suggest to add logic to check if the row you are adding if already exists in the data or not.
If not there already, then add else skip it.
Queue item will have retryno as one of the parameter you can use that
Transactionitem.Retrynumber = 3 on then side use add data row on else side ignore
Cheers
Dear @Rizwana_KM ,
If you are using excel data row as a transaction item, then below approach works for you.
In SetTransactionStatus.xaml. You need to delete the IF block----> If TransactionItem is a QueueItem (System Exception). Also need to add new IF block with config as shows in image.
It will write only once in excel row.
Br,
NikZ
Hello @Rizwana_KM
What i did is :
Added another flow decision to sequence (condition Retry>3 ) then new try catch which contain logic of send report.
Regards,
Rajesh Rane
Hi @Rizwana_KM
Use below approach you can check in data table if record already exists then skip the add data row
Not io_dtStatus.AsEnumerable().Any(Function(x) x(“ID”).ToString.Equals(in_TransactionItem.SpecificContent(“ID”).ToString))
in then part add data row and else part ignore it this way it will add the record only once even if it retries multiple time
I hope this will work for you!
Thanks
Hi @Rizwana_KM
use an if condition inside the system exception to check if - transactionitem.CurrentRetryNumber equals the max retry count (3). only add the data row when this condition is true, so the failure logs once after final retry. this prevents duplicate entries during retries.
If helpful, mark as solution. Happy automation with UiPath
