MaxRetryNumber in Re framework

Help
1

Can “MaxRetryNumber” in config file of the framework overrides the “Max # of retries” in the Orchestrator queue properties i.e if I set Max # of retries =1 & MaxRetryNumber =3 How many times the queueItem will be retried?

2

Hi @Esraa

I checked in the Framework and IF I got it right, then it is either the queue retry OR the config retry.

In your scenario, it would mean that the 1 retry for queue items will take priority and the config value will not be taken into account. I am sure it is mentioned somewhere in the ReFramework documentation, so feel free to dig in there.

You can also dig in deeper into the Framework itself and check the xaml file “SetTransactionStatus.xaml” and the part ‘Handle System Errors’:

image
image850×674 17.8 KB

image

1 Like
3

Thanks @loginerror for your comment,

The thing I understood from the “Handle System Error” workflow is that the “MaxRetryNumber” in config file will affect the queueitem retry in one case; when the value in config > 0 and < queue item retry number in orchestrator.

In other words the value in the config file is powerful only if it doesn’t work with queue items

4

image
image998×175 19.5 KB

This is from the REFramework document.

1 Like
5

I recommend not using the config file to define # of retries, but leave it to the orchestrator if allowed.

It is the same argument for choosing to use an asset over a config file setting: you want to be able to change it without publishing new versions and whatever change-audit trail you need to provide for that.

The onsly valid reason not to use the orchestrator values is security… If changing the retry by an operator seriously impacts business processes, you might want to hardcode it in the config.