Workflow Analyzer results are not same from CommandLine/Studio

When I execute Analyze Project into Studio there are 10 errors. On the same machine, when I execute the analyze with the CommandLine onto the same project, there are only 6 errors…My Studio is connected to a governance file. But I think Analyze into a CommandLine is based onto the same RuleConfig.json.
How to explain those differences ?
D:\Program Files (x86)\UiPath\Studio> UiPath.Studio.CommandLine.exe analyze -p “abc\project.json”

1 Like

Hello @KarineC!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly

1 Like

Hi @KarineC,
Yes, the analyze should be based on the same RuleConfig.json file. Can you please provide a small sample project to reproduce this issue?

Hi, apologies for reviving this old thread. But I am experiencing the same issue. Custom rules trip on Studio but not in CommandLine. Confirmed via procexp that workflowanalyzer.exe launched by commandline.exe does not load custom rules DLL. RuleConfig.json is respected, but I believe the issue lies in the CustomRules directory setting set in Studio not respected by CommandLine.