Loading

Outbound change set remains Open after upload

Publiseringsdato: Jun 8, 2026
Beskrivelse

This article explains why an outbound change set in Salesforce may remain in 'Open' status and never arrive at the destination (target) organization after upload. A change set is a deployment method used in Salesforce to move metadata (such as custom objects, fields, and Apex classes) between related orgs (e.g., sandbox to production). When an outbound change set upload appears to succeed but the status never changes to 'Closed' and the change set never appears in the target org, this is typically caused by an in-progress deployment in the source org.

Løsning

Why Does This Happen?

This behavior occurs when another deployment is already in progress in the source org. In-progress deployments from inbound change sets or external API tools (such as Salesforce CLI or the Metadata API) can lock the org's administration setup. 

When this happens, you'll often receive an error when you attempt to change other Setup configurations:

Organization Administration Locked 
The changes you requested require salesforce.com to temporarily lock your organization's administration setup. However, the administration setup has already been locked by another change. Please wait for the previous action to finish, then try again later.

How to Confirm the Cause: 

Navigate to Setup, type 'Deployment' in the Quick Find box, and click Deployment Status. Review active and completed deployments. 

Resolution:

If a deployment is still in progress, wait for it to complete, then re-upload the change set. If no deployments are active, try uploading the change set again.



 

Knowledge-artikkelnummer

000384110

 
Laster
Salesforce Help | Article