I have multiple workflows that i always use.
But recently when i try to open a certain workflow it opens the wrong one.
Has this ever hapenned to someone?
Hi @ricardo.costa ,
Yes it happens mainly due to Duplicate xaml names in different folders or studio cache issue, Fix by renaming workflows andthen reload your project or restart UiPath
Happens mostly when multiple XAMLs have the same name in different folders. Renaming them to be unique usually fixes it. Also try closing Studio, deleting the .local and .screenshots folders, and reopening the project. Also check the project.json and confirm the main entry is pointing to the right XAML.
If Invoke Workflow File is used, re-browse and select the workflow again instead of using the old reference.
Cheers
Welcome to the UiPath Community!
Yes, this can happen and it’s usually due to duplicate workflow names or multiple project folders having files with the same name. UiPath Studio may open a different workflow if the project path is not the one you expect.
Checklist:
Ensure there are no duplicate .xaml files with the same name in different folders.
Open the workflow directly from the Project panel instead of Recent files.
Verify the project folder path and reload the project if needed. Hope this will fix the issue
Welcome to the community
Can you show a screenshot..are you opening by clicking the xaml in folder or directly from the studio window?if studio window check if you are opening the correct one mostly it might be that you are selecting a wrong project
cheers
Yes, this has happened to others as well. It usually occurs when there are multiple workflows with the same name in different folders, and UiPath ends up opening a different one than expected. This can also happen if a workflow was moved or renamed recently and the reference did not update correctly, or if the project.json file has some issue. Many times it opens the wrong file when you use the Recent list instead of opening it directly from the Project panel. Restarting UiPath Studio, reopening the project, and checking the full path of the workflow normally resolves the issue.