Error overview
You may run into this Salesforce error when deploying certain ConfigData components that have lifecycle status restrictions:
INVALID_INPUT:You can't create a
[component type]with an active status. Select the draft status and try again.:Status --
This error comes from Salesforce, not Gearset.
Why you're seeing this error
Certain Salesforce components deployed as ConfigData enforce specific lifecycle status transitions. These components can only be created with a Draft status. You cannot create them directly with an Active or Inactive status.
The typical allowed status transitions are:
Components can only be created with a
DraftstatusDraft→ActiveActive→InactiveInactive→Active
Common scenario
Your source org contains a component with a status of Active. When you try to deploy this component to a target org where it doesn't already exist, Salesforce rejects the deployment because it cannot create the component directly with a non-Draft status.
This is a Salesforce platform limitation, not something that can be resolved by changing Gearset settings.
Resolution
Since status restrictions are enforced by Salesforce, the workaround requires manually amending the status value to Draft before deploying.
Option 1: Amend the value in version control (Pipelines)
If you're deploying ConfigData from a Git branch using Gearset Pipelines:
In your Git provider (e.g. GitHub, Azure DevOps), navigate to the branch containing the affected component.
Locate the file for the component.
Edit the file to change the status value to
Draft.Commit the change to your branch.
Re-run the deployment from the amended branch.
After successful deployment, manually update the status in the target org to
Active.
Option 2: Amend the value in version control (Compare and Deploy)
If you're not using Pipelines, you can still use a Git branch as your source in Compare and Deploy:
Go to Compare and deploy and select your source org and a Git repository and new branch as the target.
Run a comparison and commit the affected component to a branch in your Git repository.
In your Git provider (e.g. GitHub, Azure DevOps), navigate to the branch you just committed to.
Locate the file for the component.
Edit the file to change the status value to
Draft.Commit the change to your branch.
Go back to Compare and deploy and select your Git repository and amended branch as the source.
Select the target org and click Compare now.
Validate and deploy to the target org.
After successful deployment, manually update the status in the target org to
Active.
Disclaimer: This error is returned by Salesforce directly, rather than Gearset. Even so, we offer guidance based on our combined experience with the Metadata API. Where possible, we try to help guide you to fix or avoid this error. In the case that this isn't possible, we may need to direct you to Salesforce support for further clarification.