Using UiPath 2024.10.12
Running UiPath workflow analyzer in the cmd and getting the output as
Why tge description is coming this way?
Why i cant see Activity Name ?
And this output is not same as workflow anakyzer log getting from UiPath.
Is there any known issue
Hi, @Pinky_AG
Thus error is because required activity packages or dependencies are not installed or loaded.
Solution:
Open your project in UiPath Studio and restore all dependencies/packages, then re-run the workflow analyzer in the command line. This will fix missing assembly issues and show activity names in the output.
No…it is loaded properly. As i mentioned when i am running the wirkflow Analyzer from the studio the different logs are generating but in cmd it is different with this kind of error message
Same process : from studio log is different
This difference is expected…UiPath workflow analyzer cmd shows raw errors and exceptions, while Studio gives detailed, user-friendly logs. There is no fix or workaround needed; this is how UiPath is designed. For best readability, use Studio for logs or export results from Studio when needed
I understand that..
As you can see in UiPath stuido the workflow analyzer is not giving the same set of rules or error. For example
In Cmd workflow analyzer is giving error for “get all asstes from orchestrator.xaml” but UiPath studio is not showing any error for this xaml..there is a inconsistency
because both tools check for issues differently.
If Studio runs your workflow without error but cmd shows issues, u can safely ignore the cmd errors its just a difference in how UiPath checks files in command line vs Studio
I have some reason where i have to dependent on cmd output…just wanted to confirm if this is same for everyone ? Becauee the older version of studio was giving same output in both cmd and studio
Yes, this difference is the same for everyone using the latest UiPath Studio and Workflow Analyzer. Older Studio versions used to give identical output in both places, but newer releases have changed how errors and rule checks are handled in cmd versus Studio.
