Regarding RE-Framework with OC Queues

[killbill2 (cm)]

Hello:

Suppose I’m using RE-Framework with OC queues(in config excel, I’m setting the MaxRetryNumber to 0, so I’m using the maxretry number set in OC), and if a process transaction failed（a system exception occurs, not business exception）, there are 2 issues, I’m not sure if I understand the cooperation between RE-Framework and OC correctly.

1. If a system exception occurs and the maxretry # in OC is not reached: then the Process Transaction state will transition back to the Init State, and then Get Transaction Data state and then back again to the Process Transaction state.
2. If a system exception occurs and the maxretry # in OC is reached: then the Process Transaction state will sill transition back to the Init State, and then to the Get Transition Data state, but as the maxretry # is reached, the OC will send a soft stop signal, so the process will transition to the end process state and hence end the entire processing.

Wonder if I correctly understand the logic here?
If my understanding’s correct, then any transaction reached maxretry number, the entire process would come to a stop, is this a correct design?

Many thanks!

[tainan.ramos]

Hi,

I apologize if I didn’t understand your question correctly.
I’m assuming OC stands for Orchestrator.

So here we go.
If the setting “Max # of retries” in OC is set to 3, for example, and in config.xlsx the setting “MaxRetryNumber” is 0, the robot will behave as follows.

When a “system exception” occurs in the “Process Transaction” state and the robot is using an OC queue, it will perform the following execution.

Marking the failed queue item and incrementing the “retry number”, counter if the counter is less than the “Max # of retries” the robot re-inserts the item in the queue to be reprocessed later and then return to the “Initialization” state, goes to “Get Transaction Data” and if there are items in the queue it proceeds to “Process Transaction” again.

If the “retry number” of the queue item has equaled the value of “Max # of retries”, this item is marked as failed and the robot goes through the path of “Initialization” > “Get Transaction Data” and if there are still items in the queue > “Process Transaction”.

Each item in the queue has its own “retry number” counter and if this counter reaches its limit, if it reaches the “Max # of retries” value of the queue configuration, the process does not stop, it goes to a new item from the queue, if there are more items in the queue.

[killbill2 (cm)]

Yes, OC stands for Orchestrator
Thanks a lot, it’s a good answer, clears out my confusion!