# UiPath Solution Activate Deployment

> The UiPath Solution Activate Deployment task activates a solution deployment on UiPath Orchestrator. This makes the deployed solution operational and ready to run in the target environment.

The UiPath Solution Activate Deployment task activates a solution deployment on UiPath Orchestrator. This makes the deployed solution operational and ready to run in the target environment.

:::note
Solutions are currently supported only in Automation Cloud. Support for Automation Suite is planned for a future release. On-premises (MSI) Orchestrator does not support Solutions.
:::

:::note
This task is compatible only with `UiPath.CLI.Windows` or `UiPath.CLI.Linux` at least version 25.10 or higher.
:::

## Configuration

Use the following table to configure the UiPath Solution Activate Deployment inputs.

| Parameter | Description |
|-----------|-------------|
| **Orchestrator connection** (Required) | A service connection to the Orchestrator instance for activating solution deployment. |
| **Deployment name** (Required) | The name of the deployment to activate. |
| **Trace Level** | The trace logging level. Default: `Error`. Options: `None`, `Critical`, `Error`, `Warning`, `Information`, `Verbose` |

## Notes

- **Solution activation**: This task activates previously deployed solution packages, making them operational in Orchestrator.
- **Deployment prerequisite**: Requires a solution deployment to be already created using the UiPath Solution Deploy task.
- **Operational state**: Once activated, the solution becomes available for execution and monitoring.
- **Environment readiness**: Activation prepares the solution for production use in the target environment.
- **Orchestrator connection**: Requires a valid service connection to the target Orchestrator instance.
- **CLI compatibility**: This task uses the UiPath CLI internally and requires proper CLI installation on the build agent.
- **Minimum CLI version**: Requires UiPath CLI version 25.10 or higher for full compatibility.
- **Final step**: Typically the final step in a complete solution deployment pipeline.

## Pipeline examples

### Basic Solution activation

```yaml
- task: UiPathSolutionActivateDeployment@6
  displayName: 'Activate Solution Deployment'
  inputs:
    orchestratorConnection: 'UiPath-Orchestrator-Connection'
    deploymentName: 'MySolution-Deployment'
    traceLevel: 'Information'
```

### With Orchestrator connection and detailed logging

```yaml
- task: UiPathSolutionActivateDeployment@6
  displayName: 'Activate Business Solution'
  inputs:
    orchestratorConnection: 'Production-Orchestrator'
    deploymentName: 'BusinessSolution-Prod-Deploy'
    traceLevel: 'Verbose'
```

### Complete pipeline: deploy and activate

```yaml
variables:
  solutionName: 'MyBusinessSolution'
  solutionVersion: '1.$(Date:yyyy).$(DayOfYear)$(Rev:.r)'
  environmentName: 'Production'
  deploymentName: '$(solutionName)-$(environmentName)-$(Build.BuildNumber)'

steps:
- task: UiPathSolutionDeploy@6
  displayName: 'Deploy Solution to $(environmentName)'
  inputs:
    orchestratorConnection: 'Production-Orchestrator'
    packageName: '$(solutionName)'
    packageVersion: '$(solutionVersion)'
    deploymentName: '$(deploymentName)'
    deploymentParentFolder: '$(environmentName)'
    deploymentFolderName: 'BusinessProcesses'
    configPath: '$(Build.SourcesDirectory)/configs/$(environmentName).config'
    traceLevel: 'Information'

- task: UiPathSolutionActivateDeployment@6
  displayName: 'Activate Solution Deployment'
  inputs:
    orchestratorConnection: 'Production-Orchestrator'
    deploymentName: '$(deploymentName)'
    traceLevel: 'Information'

- script: echo "Solution $(solutionName) v$(solutionVersion) activated in $(environmentName)"
  displayName: 'Activation Summary'
```