I recently tried to deploy some changes between sandboxes using the Force.com migration tool and got the following error:

Failed to process the request successfully. Cause(ALREADY_IN_PROCESS): null: 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.

According to this question, the organization can be locked by deployments (of course) or during unit tests (seems odd to me, never seen it before). Regardless, neither of these is happening in the org I am working in. Is there documentation somewhere that lists all potential causes of an organization lock?

  • This might be of help: stackoverflow.com/questions/9491229/…
    – Bob Lopez
    Feb 8, 2017 at 23:59
  • Seems like it could be a release upgrade? Or perhaps one of the many long running re-calculations such as sharing changes, forecasting changes, picklist changes on a large object. I'm sure there are other examples.
    – Adrian Larson
    Feb 9, 2017 at 0:06
  • The bad thing is that it doesn't put request into queue (like keeping it in Pending state), but just throws that error and breaks our CI. Why doesn't it just hang in Pending status waiting for org to become unlocked(
    – wesaw
    Dec 3, 2017 at 17:37

1 Answer 1


'Org Administration Locked' error in Salesforce documentation.

Refer to the link for more detailed explanation and potential causes.

  • 3
    This is Link only answer which is considered as low quality, would you mind adding few bits and bobs? Nov 14, 2018 at 16:17

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .