When a developer publishes a package from Studio to Orchestrator without making changes, what happens in Orchestrator?

When a developer publishes a package from UiPath Studio to Orchestrator without making changes, a new version of the project is indeed sent to Orchestrator but it is not set as the active version. This behavior occurs because Orchestrator handles package versions carefully to ensure stability and control over deployed processes.

When the same version of a project is published, it recognizes that the content has not changed, and therefore, it does not activate or replace the existing running version. This allows for a more cautious approach to managing automation processes, ensuring that only meaningful updates are deployed and reducing the potential for unexpected behavior in production environments.

The handling of versioning in this way allows developers to have a consistent and reliable deployment process, ensuring that unintended changes do not affect automations that are crucial to business operations. Thus, the process upholds stability while still maintaining version history for compliance and tracking purposes.