Retry activity doesn't work with persistence

Feedback Activities
, ,
1

Hi all ,
I am facing a problem when I am using retry activity in a project that use wait and resume Activities , when I run the process by orchestrator the job paused on the first try and doesn’t try to execute the retry scope again , and the state of the job will be suspended forever.

2

@FarahEtmeh

Provide us with more screenshots where you are facing issue

That will helps us to check the issue

Thanks

3

Hi @FarahEtmeh

Could you provide a sample, newly created project that reproduces the issue?

Does it still reproduce on the latest versions of all activity packages?

4

Hi @FarahEtmeh,

I think the Retry Scope does not work in an Orchestration Process / Persistence Package because of the Interval-Function that allows the next retry to wait for a specific time.
Since I ran into the same issue as you did, I tried rebuilding a Retry Scope using a do-While loop and a delay activity.
The delay activity results in the same behavior and is also excluded in the orchestration Process doc
( Orchestration Process (uipath.com) )
@loginerror I used the Version 1.1.9 of the persistance package.

Cheers

5

Thanks @RPraschma

I think the best option for now would be to accordingly update the documentation section that you have linked. I’ll suggest an edit.

It does seem like the issue comes down to the quirks of the asynchronous execution that comes with the Persistence activity package.

I am sure our team is looking into ways to improve this experience.

6

If there is still someone out there with this issue, you have to use “No persist scope” container where you can put your retry:

image
image1055×429 12.4 KB

1 Like
7

Hello
Should I put a Persistence activity like Add Task Comment inside the No Persist Scope?

image
image760×889 17.4 KB

8

Hi ,
Did you find the solution to this problem?
If Yes Please share. I am also facing the same issue

9

I had a big in depth discussion with one of the developers at UiPath regarding this, the No Persist scope solves the issue provided you aren’t trying to retry a persistence activity, which obviously won’t work.

I suggested they make a special Retry Scope in the Persistence Activities will won’t persist and could handle all retries appropriately but it remains to be seen if that will happen.
Apparently the dev team are also working on a retry functionality in the Persistence activities to help make them more robust against timeouts and 501 errors etc.

In the meantime, the only workaround I know of is to make a pseudo retry scope as suggested above by using a loop in a flowchart and a try catch.

2 Likes