"Invoke Workflow File" between private workflows not working in a library project

Help Studio
#1

Hello,

I’m testing a library project as below;

NewActivity.xaml calls Sequence1.xaml and Sequence1.xaml calls Sequence2.xaml.
NewActivity.xaml - public, Sequence1.xaml and Sequence2.xaml - private

When trying publish, the following errors occurred.

12:57:18.5069 => [ERROR] [UiPath.Studio] [35] Unexpected error has occurred during the library compilation process:
The following invoked workflows are missing:
C:\Users\tom.lee\OneDrive - UiPath\Documents\UiPath\NestedInvokeWorkflowFile\Sequence2.xaml
Called from the following workflows:
C:\Users\tom.lee\OneDrive - UiPath\Documents\UiPath\NestedInvokeWorkflowFile\Sequence1.xaml

It doesn’t seem that a private workflow’s calling another private workflow is working in a library project.

Anyone who faced and resolved this kind of error?
If so, please share it with me.

Thanks,

Tom

Forum Engagement Daily Reports
#2

@Tom_Lee

Hello Tom,

I tried that and in my case it works without any problems, the compilation creates a NuGet package. As far as I can say works a call of a private workflow which calls another private workflow.

Best regards
Stefan

image
image720×331 16.4 KB

#3

Hello Stefan,

Thanks for your reply, but you need to make PrivateSequence01 and 02 files Private.
Then the errors should come.

Thanks,

Tom

1 Like
#4

Same problem here…

#5

@Tom_Lee

Hello Tom,

not possible to reproduce the error with 21.4 in my case.

Start with …

image

… and extract any sequence as workflow, all private flags are set.

image

Publishing and executing works without failure.

Please share your project.

Best regards
Stefan

#6

We have the same issue. Libraries in 21.10 seem to be having this same issue, where invoking a private workflow within a private workflow will break publishing the project.

#7

I m having the same issues. It was working fine before we updated the version to 2021.10 :frowning:

Any workarounds for this problem ? I have to update the library project and it’s not letting me do it…

#8

My teammate encountered this issue recently as well. They reached out to our Technical Account Manager who subsequently reached out to the product team. It seems this is a known issue that will be corrected in a future release (no ETA was shared). The workarounds provided were to 1) make the private workflows public or 2) don’t use a private workflow and instead place all logic within the public workflow. I believe my teammate opted to make the private workflows public but place them in a separate folder with a name such as “Private” to help avoid confusion.

#9

My teammate followed up with our TAM, the following is the response they received.

I just checked the product board confirm that this is going to be fixed in the 2021.12 release which will be available this month.

#10

Hi @loginerror

Any update on when this bug will be fixed in the enterprise version?
Would like to know as I am waiting to update the version.

Thanks