Preprocessing issue in project (looking for deleted workflows)

[SenorChang]

Hello community,

I want to reuse a project I have worked on quite a long time for a new project. I want to delete the workflows of the old project and build new workflows.

However, if I try to debug I always get the message in preprocessing that my already deleted workflows cannot be found. I am sure that I deleted/disabled the parts where the workflow is invoked and I don’t understand where it is configured to search the workflows.
If i put back the deleted workflows the debugging works again.

Can someone please help?

[mkankatala (Mahesh Kankatala)]

Hi @SenorChang

Delete all the Invoke Workflow activities that were used to invoke the old workflows, as these activities which searching for the old workflows and failed.

Hope it helps!!

[Anil_G (Anil Gorthi)]

@SenorChang

Commenting them would not help…you nees to delete the invokes

Cheers

[SenorChang]

I already deleted all the invokes but it is still not working. Besides that everything is so buggy when I downloaded the package from Orchestrator and open it. It is a nightmare with those dependency issues.

[Eric_Alvarado]

Hi @SenorChang
Make visible all files

Also, you can use ‘Find References’; it will show where the workflows are being used/invoked

[SenorChang]

What will be the effect if I enable hidden folders? I deleted the workflows anyway. If I do “Find references” I get the same output as in your screenshot. I think that there is something messed up in initialization or whatever.

What I also noticed is that if I try to use an UI activity and click “Indicate on screen” nothing happens. I can only go via Ui Explorer. Something is really messed up in Studio.

[mkankatala (Mahesh Kankatala)]

what exact error it was showing when you start executing your workflow, if possible took a screenshot of output panel and share with us… @SenorChang

[SenorChang]

I narrowed down the issue with the find reference option. The deleted workflows point to the process.xaml and to sequences that don’t even exist anymore. I also tried to delete the old process file and replace it with a fresh file from robotic enterprise framework. The reference still persists.
The handling of dependency compatibility is very poor I have to admit (it is not the first time that some activities disappeared after upgrading the depedencies. I think this happened here again). At first no core activities were working and you have to manually try to reload and upgrade the dependencies. I think starting with a fresh process and manually copy&paste will solve my issue faster than troubleshooting I guess…

[mkankatala (Mahesh Kankatala)]

Okay @SenorChang

I see that one of the dependencies in the screenshot is a runtime dependency. Install the UiPath.System.Activities package from Manage Packages. For any runtime dependencies, install their corresponding design packages.

Installing design packages will enable all activities for use.

Hope it helps!!

[SenorChang]

Thank you. I downgraded the package and now it seems to work. Now I have again the issue with the broken core activities. I have no import argument function for the invoke activity. This is really getting frustrating.

[ashokkarale]

@SenorChang,

Install package UiPath.System.Activities. when you download the package from orchestrator it contains only the runtime versions…

Install the full version of the package and you will see the activity normal.

[mkankatala (Mahesh Kankatala)]

Install the UiPath.System.activities package first… @SenorChang

Then every activity will appear.

Hope you understand!!

[SenorChang]

Thank you so much! It seemed that only installing the package itself does not help but I had to remove the runtime dependencies. Now it works.

Thanks to everyone who assisted in this topic. Again something new learned.