When using REFramework without Orchestrator access, what is the best practice to ensure that a transaction will be retried in case a System Exception occurs during its processing?

When using REFramework without Orchestrator access, what is the best practice to ensure that a transaction will be retried in case a System Exception occurs during its processing?

@Kanu_priya_Munja1,

Set the MaxRetryNumber in the Config.xlsx file to a number greater than 0

This will work like Queue’s retry mechanism for non queue based transactions.

Thanks,
Ashok :slight_smile:

Set MaxRetryNumber in the Config.xlsx file to a number greater than 0

@Kanu_priya_Munja1

check this reference

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.