I encountered a very weird behavior while working on one of my custom libraries. I have 2 libraries that are responsible for interacting with a system. One is coded and the other is not. I worked on the one that is not coded. They have different names and project ids.
I updated my non-coded library several times that day without any issues until it suddenly didn’t work anymore. After investigating the cause, I found that the libraries seem to be mixed up. My activity library suddenly shows the same activities as the connector library (without using the activity layout). I don’t understand that at all. I tried several things to fix it, because I thought it was related to the publishing, but soon realised that it doesn’t matter how often I publish the activity library and what version number I use. It always doesn’t work.
Does anybody know what the reason could be?
Both libraries are saved in a sharepoint folder that is synced to my system but since I was the one changing and saving them, I doubt that this is the cause of it.
The names are:
xyz-activities (projectId: 03ad28af-2b60-4c7a-8ccf-7f25c3d094d9)
xyz-connector(projectId: 2cef4199-2a08-41a5-a5cf-37139c27141d)
Here is a screenshot of activities of the current broken version:
Quick update: I now tried to create a new library and only copy the workflows from the old library and then published from that new library with the same name to the next version. But either the problem lies within the workflow files or the project using the libraries is broken.
I now used an existing project and added the library with the new version and it actually is broken in the other project as well. This indicates to me that the problem seems to be related to the activities themselves. Mhm
I now also tried to put the library in orchestrator and use it from there, but that also didn’t fix the issue.
Pls try check for activity version conflicts or dependencies in the new library. Also clean and rebuild both the library and the consuming project. If the problem persists, consider isolating and testing individual activities to identify the root cause.
when you say mixed up the workflows are copied from one library to another? if so that is not a good way to do it as dependencies might be different across
Try to close the Studio library project.
Edit the impacted xaml/json files of the libraries in Notepad++/Notepad, correct the incorrect details, open in Studio, republish, and test the behavior.
I recreated the project that uses the library as well as the library itself without copying the files at all. I published the library under the old name (xyz-activities) and a new version number aaaand the problem persisted.
I was now suspecting that it may be related to the location of the library, as it is located on a sharepoint (synced folder on the pc). But that also didn’t fix the issue.
I now published the library with a new name (xyz-ui-acitivites) and that finally fixed the issue.
This surprised me. I wouldn’t have expected that UiPath uses the actual name. This happened probably because I had a previous version of the activities library that had the activites that are now in the connector library like Download public report, because I only realized later, that I needed coded workflows for those activities. I later removed those versions manually, but there must be somewhere a trace left of those. So my take away is, to never delete previous versions or a library manually ever and if I need that, I need to rename the library.
