I have read many topics on Retry Scope but i don’t have ant perfect example. Actually my process is going on and in between suddenly i get network error popup message so application will be closed and it will reopen. So i have following questions -
i have put try catch in retry scope and i have given a condition like, element exists. Where i am capturing my screen and before that network error popup comes every time. So i have given output as exists. If bool exists true then nd then it will work in that existing window or else it will throw an exception and will retry the scope. And whenever it reopens then my first transaction will be skipped and it will automatically take second transaction, as exception occurred on first transaction so is it true?
I wanted like, it should retry the same transaction 3 times.
other thing is, where do i increase that retry loop? Like, if i want that it should retry 2 times only, then where do i increase it ?
Please explain me in my scenario
I’m not doing it through orchestrator but through scheduler.
Hi there @hemal,
While you can certainly use the retry scope for this, I would recommend against it.
You would be better off fitting your process into the ReFramework and utilising its in-built retry mechanic, which will work without Orchestrator, performing local retries.
Thanks for your response. I am trying through your solution but I want to know that where did you get this IsTrue activity ? which package do I have to install ?
I got it. IT’s under Workflow Manager activities. I have a doubt like, where do I increase my retry scope ? I am giving numberoftries -2 then it’s not going in again. it’s ending the process.
@Mr_JDavey thank you so much
Now i got the exact meaning of this activity. The thing is when transaction is going on at that time it will just retry it but it will never reopen …for that we have to initialize again. Right ?