Error overview
You may run into this Salesforce error when deploying certain ConfigData components that have lifecycle status restrictions:
INVALID_STATUS:Can't change status from Draft to Inactive.:Status --
This error comes from Salesforce, not Gearset.
Why you're seeing this error
Certain Salesforce ConfigData components, such as those related to Revenue Cloud Advanced (RCA), enforce specific lifecycle status transitions. You cannot transition a component directly from Draft to Inactive. It must go through the Active status first.
The typical allowed status transitions are:
Components can only be created with a
DraftstatusDraft→ActiveActive→InactiveInactive→Active
Notice that there is no direct path from Draft to Inactive.
Common scenario
The component exists in both your source and target orgs, but with different statuses:
In your source org, the component was activated and then set to
InactiveIn your target org, the component is still in
Draftstatus
When you try to deploy, Salesforce rejects the status change because the transition from Draft → Inactive is not allowed.
Resolution
To resolve this error, you need to manually activate the component in the target org before deploying. This allows the deployment to perform the valid Active → Inactive transition.
Steps to resolve
Log in to the target org in Salesforce.
Navigate to the component that is failing deployment.
Change the status from
DrafttoActive.Return to Gearset and re-run the validation/deployment.
The deployment should now succeed, as the transition from Active → Inactive is allowed.
Alternative: Match the source status
If your goal is simply to get the component deployed and you don't specifically need it to be Inactive, you could instead:
Change the status in the source org to
Active(if it's currentlyInactive)Re-run the comparison and deployment in Gearset
This would result in a Draft → Active transition in the target, which is allowed.
Disclaimer: This error is returned by Salesforce directly, rather than Gearset. Even so, we offer guidance based on our combined experience. 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.