Org Administration Locked Error in Salesforce — Sharing, Custom Field, or Metadata Change in Progress

This is not an error. This is expected behavior designed to protect data integrity. Salesforce temporarily locks the relevant setup area while a large change is being processed. Sharing changes lock only sharing setup; custom field or object changes lock only custom field/object setup.

Why the Org Lock Occurs

When an administrative change that affects a large number of records is in progress, Salesforce locks the relevant setup area until the change is complete. This ensures that simultaneous conflicting changes do not corrupt data or metadata.

Changes That Trigger a Sharing Lock

The following actions trigger a sharing administration lock:

• Changes to the Role Hierarchy
• Changes to the Sharing Model
• Mass reassignment of Account or Sales Teams
• Role create, edit, or change
• Territory create, edit, or change
• User create, edit, or change

Changes That Trigger a Custom Field/Object Lock

The following actions trigger a custom field/object lock:

• Any create, update, or delete of custom fields or custom objects
• Replacing picklist values
• Simple changes such as editing a custom object description

ANT and Metadata Deployment Locks

The following metadata deployment scenarios also create or extend an org lock:

1. Admin changes made from the Salesforce UI can create an Org Lock.
2. ANT deployments can create an Org Lock.
3. A terminated ANT deployment does not immediately terminate the server-side process — the Org Lock continues until the process completes or recovers.
4. A timed-out ANT deployment means only the client-side wait has ended; the server-side process and Org Lock continue until complete. To avoid timeouts, adjust timing settings in your build.xml file.
5. A heap error during an ANT deployment also does not terminate the server-side process. Adjust Java/ANT heap settings in your environment to prevent this.
6. Simultaneous ANT deployments by different individuals can be blocked due to Org Locks.
7. If users are on a network with a Reverse Proxy or network traffic control (such as WebSense), clicking Run Tests or Deploy may submit duplicate requests. Create a network exception to allow direct traffic to Salesforce to resolve this.

How to Check What Triggered the Lock

Navigate to Setup > View Setup Audit Trail to review recent administrative actions and identify which change triggered the lock.

When to Contact Salesforce Support

An Org Lock is self-resolving. Do not log a Salesforce Support case unless:

• The lock exceeds 3 hours, or
• The lock is significantly impacting a critical project.

When logging a case, include: the affected org, the username experiencing the issue, Salesforce debug logs and ANT logs, the ANT package that caused the problem, and the Setup Audit Trail.

Best Practice

Change management, change control, and scheduling procedures are essential when making administrative changes as a team. An Org Lock has no manual removal option — there are no options to remove or delete an Org Lock.