2019.10 - Invoke Workflow error

[Srishti_saxena]

I did it still the issue persists

[Srishti_saxena]

what if i want to invoke that orchestrator workflow with create form task and wait resume in a process work flow .Im getting issue in that scenario

[loginerror (Maciej Kuźmicz)]

@Srishti_saxena

I think these two are still valid:

2019.10 - Invoke Workflow error

For the time being, long-running workflows must be created using the Orchestration Process template in Studio (see below) due to slightly different settings in the project.json file. [image]

2019.10 - Invoke Workflow error

I looked around a bit and it looks like Long-running activities part of the UiPath.Persistence.Activities package can only be used in an Orchestration Process entry point, the file marked as Main.xaml . See here, the Best Practices part: From what I’ve found out, this is the cause of the error.

This means that you cannot use the Persistence activities from within an invoked workflow.
Could you show a screenshot of what you are trying to achieve if that’s not the case?

[Srishti_saxena]

yes sure
1.This the orchestrator process where I have created a" create from task" and resume activity

2.This is simple process where I am invoking that orchestrator process

But I am getting error

[AshwinS2 (Ashwin S)]

Hi @Srishti_saxena
Can you update the package

Thanks
Ashwin S

[loginerror (Maciej Kuźmicz)]

I think you cannot use the Wait for Form Task and Resume activity in an invoked workflow. These persistence activities only work from the Main.xaml (or any workflow in you project that is marked as the main one).

[kwoxer (Curtis Mosters)]

I ran into the same issue. Well I think this is kind of nonsense that the Wait for Form Task and Resume needs to be in the Mail.xaml file.

If someone is using the ReFramework like we do, this is kind of impossible as the Process is in an extracted Process.xaml file.

So how to solve this now? Is there another way to resume? And if not, what is the sense of resuming something that may not be in an invoke.

[Oana_Georgiana_Vasile]

@loginerror

age can only be used in an Orchestration Process entry point, the file marked as Main.xaml .

did you found a solution for this?

[kwoxer (Curtis Mosters)]

Yes, I extended the ReFramework. But the changes were huge!

Basically the idea was that I throw a custom exception in the process workflow. This exception contains the TaskObject as data parameter. And do not forget to serialize the object.

And then back in the main workflow I catch the custom exception and and deserialize it back. And now I have the TaskObject in the main workflow and can use it.

But I worked like a whole week on the implementation.

Sadly that this does not come directly from UiPath. Hope you got the idea.

[Shashi_Kumar1 (Shashi Kumar)]

hi all
here is the fix for that error
it work to change to the following setting in the project.json file?
“supportsPersistence”: true

[RanaMuhammadAli (Muhammad Ali)]

Solved the problem in two steps
1: First of all go to the project settings.
2: Then enable the Supports Persistence.

[AlexanderERoss (Alexander Ross)]

Great

Is there a reason for this? This just wasted 2 weeks of project time. So there’s no way to adjust the project settings? Or anything else to get it working?

EDIT: Tried looking at Project Setting, Persistence is set to on. Frankly this is a bug.

[AndyMenon]

Hello @AlexanderERoss ,

I recorded these screen shots a while ago in a document. Therefore I must have run into these issues in the past. Can you see if these help? I’m shooting in the dark here, but one never knows.

Name of output object is set differently from the input:

[MigT (Miguel Thibaut)]

Hi @RanaMuhammadAli,

My team used this settings and UiPath prerequisites but I have the same issue that @kwoxer.
I just find a new Reframework Template, but that means that we need to rework all the process to adapt it.
So if one of you have an idea before to help us, I will be grateful to him.
Thanks.

[Jay_Jathaul]

Were you able to get a solution/fix for this issue?

[marina.dutta]

Hi @kwoxer,

I am having the same issue .My create form and Task and Resume is in the Process workflow. How to make changes to run in Main workflow.

I am getting error “System exception. Max number of retries reached. An extension of type ‘UiPath.Activities.Contracts.Persistence.IPersistenceBookmarks’ must be configured in order to run this workflow. at Source: System.Activities”

I have renamed my main workflow as UC004_CreditRollover. Can you help on this

[Ritaman_Baral]

similar issue facing here…need assitance…without wait for resume it is working fine…But with wait for resume the invoked workflow is fialing…I have used both of them inside invoke workflow

[mateuszmacheta]

Sorry for response after two years but I think it may be valuable for other people who still get the same issue.
I came across the same limitation and I just split Process.xaml into two parts: Process.xaml and Process2.xaml - then put Form activities and Wait for Form Task and Resume. This way you can execute whatever’s in Process2.xaml according to output from form response.
I’m not sure what your approach with exceptions achieves, definitely requires more steps to make it work. What was specific requirement that made you choose this approach?