Orchestrator Arguments when published via Azure DevOps

Hello There,

Since the last update of Studio (new installed Version: 2021.4.4) arguments don’t seem to appear for new robots in the Orchestrator. I read a few similar questions in forum about this issue but couldn’t find any answer. The project Json is neither reflecting the new Ui-Version number not the arguments List (Other parts such as information about packages is however being updated). Is there still some sort of Problem while publishing via DevOps ? appreciate your support.


Hello @Hara_Gopal!

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

Found the answer, its a on-premise setup and the build-server has an older version of UiPath Studio …

Hi @Hara_Gopal,

Sadly not only via Azure DevOps, this happens when we publish directly via Studio to On-Premises Orchestrator as well. We thought the Azure DevOps UiPath Pack would fix this issue, but it is persistent.

For others facing the same issue:
Our temporary solution is to manually add arguments to project.json for each project and later commit it to TFS and via Azure DevOps deploy to Orchestrator. Only then can we populate the arguments for the published processes in Orchestrator.

You can add the arguments key in project.json after modernBehavior key like this

  "fileInfoCollection": [],
    "modernBehavior": false

  "arguments": {
    "input": [
        "name": "in_OrchestratorQueueName",
        "type": "System.String, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c562324e089",
        "required": true,
        "hasDefault": false
    "output": []
  "expressionLanguage": "VisualBasic",