Error While Publishing Process to Orchestrator - " Object reference not set to an instance of an object."


When the package is downloaded from Orchestrator and uploaded to studio for enhancement and then publish back the newer version back to Orchestrator then error might throw " [Error: System.NullReferenceException: Object reference not set to an instance of an object]

Root Cause: Check any files/Folders in your process flow have %20 as this will be automatically created wherever “space” is present in files/folders of your process. This will occur when the package is downloaded and extracted the process files.

Solution: Rename the folder/files which are have %20 without space OR use “_”(underscore) instead of spaces between the file/Folder names.
And then publish again so that issue will be solved.

Also the coding standard to be followed on naming file/folders should be no spaces between the words.

Hello @ARUN6KUMAR007!

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