@Srini84
The issue is different. My project has no validation error and its running properly from studio.
Only facing the above error while trying to publish it to orchestrator
As you are using the beta version of the Uipath studio, we can expect this kind of errors, so you better check with a stable version studio might it helps
I’m facing exactly the same issue. I can publish other processes to the Orchestrator without any issue and the workflow that I’m trying to publich has no validation errors at all.
However, the error message “Object reference not set to an instance of an object.” keeps appearing every time.
We are running into the same issue here as well.
When downloading the package from orchestrator, opening it in studio and re-uploading it without changing anything, this error will also occur.
Hope somebody can dive into this @loginerror ?
If we found some solution i will update you guys here as well.
Just for my knowledge. How does this work and where lies the error?
We have never noticed it before, so it must happen when downloading packages from orchestrator. Does this mean its an orchestrator issue?
Just to update on the issue - it was deemed as “no fix” due to the fact that unzipping your project files is an unsupported scenario. Packaged project’s only purpose is to be a run file.