What is the default retry times in REFramework?
The default MaxRetryNumber
from the Constants sheet of the âData\Config.xlsxâ is 0
.
Yes its 0 but the process retries?
0 indicates there is no retry?
My understanding is that without changing that value it does not retry. UNLESS you are using an Orchestrator queue.
I am working in queue
Then that would depend on your settings for that particular queue.
Hi @Sweety_Girl
no worries
âif the queue is mentioned with any default value of number of retries then it will retry to that number
âor based ont he value we set in set transaction status here will take it forward
Kindly have a view on this thread buddy
Cheers @Sweety_Girl
If there is a retry number specified in the orchestrator queue, then that overrides whatever is set in the config file.
If the config file has 0 max retry. But the transaction is retried?
If 0 will it change the transaction status to retried and newâŚ
It again process it if again fails,
It it changed to retry and again new?..
Will it process in such a way ?
How is your queue in Orchestrator configured?
Fine
let me explain you elaborately
âusually we use retry option is used to handle exception in a robust way based on the type of exception either system or application or busines exception
âin that if we have any application exception it will make a retry
âRetryNumber is usually a global variable defined in the variable panel
âSetTransactionStatus.xaml is the xaml where the transactionnumber is incremented usually when everything goes good, like io_TransactionNumber gets incremented when the transaction is correct but if the transaction fails due to application error instead of this io_transactionnumber getting incremented, io_retrynumber will get incremented which we can find âHandle system errorâ sequence
âso this is how it works in REFramework
âin our case we need to check with the config file along constansts sheet and check with the value of MaxRetryNumber as it must be 0 if we are using queues as we would have mentioned there in the queues with max of retires option, or if its greater than 0 been mentioned in the config or queue it will retry till that as maximum limit
âso kindly check once with the queue we have created is it given with any max of retry values and also with config file as well
you are almost done,
âif still we are not clear , run the process in debug mode and set the speed of process as 3/4 hear and run the process so that it will run a bit slower leading us to know the execution of the process and enable highlight option as well under OPTIONS in execute tab
hope this would help you
Cheers @Sweety_Girl
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.