The best place to log state of transaction after last retry

Help Studio
,
1

Hello guys,

I would like to send an email report to a customer giving some basic statistics about how many items were successful, how many resulted in SE etc. My problem is SE itself. As it’s going to retry, I only want to log whether it was succesfull or not after the last defined retry aattempt. Where exactly should I do it?

Cheers,
W

2

Hi @witold.p.sobkow,

You should check the retry count. Once the retry attempt reaches the maximum allowed (RetryNumber = MaxRetryNumber), you can safely count it as a final System Exception and send the email report, since no further retries will occur.

Thanks

3

Hi @witold.p.sobkow

Pls use queue‑based retries and log only in process.xaml after final failure by checking transactionItem.RetryNo equals Config.MaxRetryNumber before calling SetTransactionStatus (Failed), so you count SE only after last retry.

Happy Automation

4

We would need some more details e.g. implemented process patterns …, QueueItem design like Reference…

In general it can be counted:

  • with a custom count logic
  • using the Orchestrator Rest API to retrieve the count /relevant QueueItems to count

Also, keep in mind. Depending on when the retry is executed again, the initial processing Job is already executed and will omit the QueueItem for the count, as it is marked to get processed later.

5

Does a queue item created as a result of a retry, hold an information about being a result of a retry or retry counter is only valid for a specific run and is held in runtime variables?