Retries in Orchestrator or config file

We have been keeping retry number as a value in our orchestrator queues for quite a while now, and our framework is ofc build for this.
Today someone asked me “what is the benefit of having the retry number in orchestrator vs in the config file” , and I must admit I couldn’t give a clear answer.
Can someone here explain me the differences between the 2 ways?

Ideally both are same.
When orchestrator is not used, the config file retry will be used.
When orchestrator is available, this option is set in Queues.

Other than this, you can have more information when the orchestrator is used like how many times the transaction is retried, why the transaction failed, you can postpone the transaction item etc.,

Karthik Byggari


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