Solutions user guide

DELIVERY:

Last updated Feb 18, 2026

Deploying a solution

This step is typically performed by an administrator.

Note:

A solution package published from Orchestrator or Studio Web can be deployed to either and Orchestrator tenant or a Personal workspace.

If you publish a solution package from Studio Web to your Personal Workspace, deployment occurs automatically. If any issues occur, see Debugging solutions in the Studio Web user guide.
To deploy a solution in Orchestrator, follow the steps below.

Step 1. Select the deployment source

Tip:

You can also deploy solutions in your Personal Workspace. In this case, navigate to the Solutions tab in your personal workspace.

Select the Solutions tab at the tenant level.
Select or provide the solution package. Consider the following scenarios:
- If the package already exists in your tenant or personal workspace, select an existing solution package.
- If you want to create a new package from your project, create a new solution package.
- If you are transferring a package from another tenant or environment, upload a solution package.
Deploy the desired version using any of the following options:
- Select + Deploy from the Deployments tab.
- Select Deploy from the corresponding row in the Packages tab.
- Select the menu icon (⋮) in the Packages tab and choose Deploy.
- Use Quick Actions from the Orchestrator homepage and select Deploy.
- From a folder, select Actions > Add > Solution Deployment.
- Deploy directly from the Package versions page.

Step. 2 Configure deployment details

On the Deploy a solution page, review and update the deployment details as follows:

First, fill in the following required fields:
- Package: Choose the package you want to deploy. Once you select a package, the Version field displays details such as package version, publish date, description, and author.
- Deployment name: Enter a unique name.
- Location: Choose where the solution folder will be created - whether to Install as root folder or select an existing folder.
  
  For more information about folders, see Folders page in the Orchestrator user guide.
For the optional fields, expand Advanced Options.
1. If needed, turn on the Use custom solution folder name toggle and enter the appropriate solution folder name.
2. In the Activation strategy section, select one of the following:
  - Now: activates the deployment immediately.
  - Later: installs the deployment but leaves triggers disabled.
Select Deploy to orchestrate the deployment.

If additional configuration is required, the configuration screen is displayed.

Step 3. Review, configure, and validate the solution

After configuring the required and optional fields on the Deploy a solution page, you can:

Select Deploy to start the deployment immediately, or
Select Review to open the Solution installer and further configure the solution components.

In the Solution installer, you can:

Review solution components, properties, and files
Filter properties from the Display dropdown
Link existing components
Save the solution as a draft
Validate the deployment configuration

Re-use and link to existing components (optional)

During the deployment of a solution, all required components are created in the target environment by default. But if some required components already exist in the target environment, you can link the solution to those components instead of creating new ones.

Consider the following before proceeding:

This functionality is available for Assets, Storage buckets, Webhooks, and Queues.
If a component with the same name already exists in the tenant, you can:
- Keep the existing component and not create an additional one.
- Keep the existing component and add additional new fields from the solution (existing fields are not altered).
- Rename the conflicting resource in the respective service.
- Rename the resource in the solution deployment, if possible.

To link an existing component, follow the steps below.

On the Deploy a solution page, select Review. You land in the Solution installer, on the Components page.
On the left side, select the component you need and then select Link to existing.
On the Link to existing process dialog, select the component you want to link to.
Select Link.

Step 4. Monitor a deployment's status

After selecting Deploy to orchestrate the deployment, you can begin monitoring a deployment's status.

A deployment can succeed or fail. You can monitor the deployment status from the Deployments tab.

Status	Behavior
In progress	The deployment operation is in progress.
Successful	The deployment completes successfully and all components are deployed.
Failed	The deployment fails and an automatic rollback is performed.
Failed Rollback	The deployment fails and some components require manual cleanup.

For details about all statuses, see Checking the deployment status.

Step 5. Activate deployments

Note:

If the solution contains apps and they are not activated using the provided link, the deployment activation fails. See the Orchestrator and Apps documentation for detailed instructions.

After a deployment finishes successfully, Orchestrator automatically evaluates activation readiness. The deployment appears in the Deployments tab with one of the following statuses:

Inactive (Ready to activate): No additional configuration is required. Select the More Actions icon, and then select Activate deployment.
Inactive (Needs setup to activate): Additional prerequisites must be completed:
1. Select the More Actions icon and then select Set up activation.
2. Review activation validation results.
  - Add accounts and assign roles.
  - Add machines to solution folders.
  - Define account-machine mappings, if needed.
  - Define asset values per robot, if applicable.
  - Activate apps used in the solution.
  - Fill in bindings for process-type components, if applicable.
3. Resolve listed items.
4. Select Validate.
5. Select Activate.