Deploy or publish a solution from Studio Web using the toolbar's Deploy button, which also provides a dropdown option to publish without creating a deployment.

The Deploy button in the Studio Web toolbar packages and deploys a solution in one guided flow, and is the default action. Select the dropdown arrow on the Deploy button to Publish the solution instead, which packages the solution and publishes it to a feed without creating a deployment. Use Publish when you want to deploy the package later from the Manage tab or from Orchestrator.

Both options open a panel with a WHAT WILL HAPPEN sidebar that previews the steps for your specific flow before execution begins.

If you lack a permission, the form disables the related option and names the missing permission. For the messages, see Missing permissions in the form. For the Orchestrator roles that grant these permissions, see Getting started with Solutions.

Use this procedure to package and deploy a solution in one flow.

Result: The panel runs through the steps in sequence. When all steps complete, the sidebar shows green checkmarks and the main area displays Deployment successful — Solution [name] v[version] has been deployed!

From the success screen:

A Logs panel at the bottom shows the timestamped deployment output. Select Copy to copy the full log.

Use this procedure when you want to package the solution without creating a deployment.

Result: The solution package is published to the feed. The panel shows Publish successful and the message Solution [name] v[version] has been published!

From the success screen:

The package appears in the Versions tab in the Manage view and in Orchestrator under Solutions > Packages. A package published to a folder feed is available only within that folder's hierarchy. To deploy the published package later, use the New deployment button in the Manage view. For more information, see Managing deployments.

The Deploy and Publish forms check your permissions before you submit. The form reacts in the following ways when a permission is missing:

Select a different feed or location, or ask an administrator to grant the permission named in the message. You can still publish a package when you cannot deploy it.

In addition to publishing a full solution, you can publish individual RPA workflow or App projects from within a solution. This lets you update a single project's NuGet package without republishing the entire solution.

To publish an individual project from a solution:

The project is published as a NuGet package using its existing publish bindings.

You can publish test cases for an RPA workflow project that is part of a solution. This option is available in both Cloud Workspace and Local Workspace solutions.

To publish test cases from a solution:

The test cases are published as a NuGet package. The behavior matches publishing test cases in Studio Desktop.

The publish history panel in a solution project lists all published versions. Selecting a version item expands it, showing icon buttons with tooltips for the following actions:

If a publish failed, the expanded item shows an error message. Select Copy error text to copy the error message.

Version items are not expandable while a publish is in progress.

Use this procedure to activate a deployment that was installed but not yet activated — for example, when Activate immediately was disabled during deployment, or when a deployment shows the Inactive (Ready to activate) status.

Result: The activation runs immediately. When complete, the panel shows Deployment successful — Solution [name] v[version] has been deployed! with the same post-deployment actions available: Back to build, View deployments, Go to folder, and Start job. The deployment status in the grid updates to Active.