just a question, why, in REFramework, the activity that load queue is inside a try catch innested in a retry scope?
Is useful to have? For which reason?
can you please provide more details about the activity you mentioned?
If you want to know, why one sometimes uses the try-catch activity over the retry scope: sometimes you just don’t want to retry a failed activity (e.g. if you know, that a retry will definetly not solve the problem).
They reason theres a try-catch inside the retry is so that each time theres an exception, the “catches” section allows uipath the print out the exception message, then it will rethrow the exception so that the retry scope will retry it.
If theres no try catch, you wont know why “get transaction item” fails, untils the whole retry scope fails
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.