Best practice long running processes

Hi all,

are there any best practises to use the UiPath.Persistence.Activities like “Create Form Task” and “Wait for Form Task to Resume” for an process developed in the Robotic Enterprise Framework?

What process i’m thinking about:

  • Dispatcher: Grabing Data from an application or email, validation of the data, if data is complete add to queue, if not complete create a form task
  • Performer: Grabing queue items and work one by one

Kind regards

Were you able to figure this out and use Persistence activities for bringing-in human interaction ?
Here are few best practices on using this activity pack (specifically wait and resume* activities )


Hi @Liji,

thanks for your answer. No, not really. I can use the Persistence acitivities in an orchestration process, but that doesn’t help me out. As i wrote i would like to use the Robotic Enterprise Framework for Dispatcher and Performer with a queue in between.

I could do it without the framework, but then i will miss the nice features of it like retrying, Exceptionhandling etc.

Any suggestions?

In the latest studio version, you could go to project settings > Support persistence can be enabled for a non-orchestration process as well. But there are some best practices to take care while using persistence activities like 'Wait & Resume* ', particularly about usage of such persistence points only in main.xaml, data serialization pre-requisite of workflow variables in the same scope of such persistence points. Alternative will be to move non-serializable content out of the same scope of wait and resume activities, through invoke workflow or in a different sequence itself.


Thanks @Liji will try that if i can manage to implement the persistance activities into the statemachine of the framework.

maybe you can help me with some other point too. How can i integrate a dynamic data table into a form via the persistance activities? The columns of the data table are fixed, three in total, but there can be a dynamic amount of rows. one column of the data table needs to be editable. the other two must be not editable.

Does that mean Persistence activities cannot be used with in REframework in 2019.10 Studio version

Hi @AnaC,

for me the setting mentioned by @Liji is there at studio version 2019.10.4:

But didn’t test it till now.