[SalesForce] Organization Administration Locked…

After having my Developer Console not be able to save a class that I edited, I faced this error message when trying to edit/save the class directly in the browser:

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."

Any idea what is causing this and/or what I can do to fix it?

Thanks!

Best Answer

This usually means:

Something is being deployed via API (check Setup -> Monitor Deployments)
Something is being deployed via changesets (Setup -> Deploy -> Inbound change sets)
You're running some unit tests.

Your request (from developer console, Eclipse or whatever) might have been canceled / timed out but the deployment still runs. One of these means should give you a hint what's going on.... You might also check setup aoudit trail if the condition persists.

If your class failed to save but it seems to be still checking - maybe you've modified something "big". Will many visualforce pages / apex clases that rely on this class suddenly become invalid because you deleted a lot? In that case it might be worth a while to help SF dependency checker by commenting out majority of these VF classes before saving your main change...

Related Solutions

[SalesForce] Error when reading metadata: INVALID_TYPE: This type of metadata is not available for this organization

I think you need to use Tooling API instead.

I'm using JSForce for this.

connection.tooling.sobject('ApexClass').retrieve('01p7R000007Axk8QAC', (error, result) => {
   
});

[SalesForce] Scheduled Apex not consistantly executing, sending emails

Things to think about...

Since the scheduled job has to execute under some user, you can set up debug log for that user and monitor for errors.
There is a limit on outbound Apex emails per day; perhaps some other job has exceeded the limit before the job in question has executed
There could be some query timeout or other catchable exception and the code as written doesn't fail gracefully

With the exception of limit exceptions, asynchronous code should use try-catch to ensure that every exception is caught and some diagnostic log is written for later examination. Such log could be an email to the sysad or and/or writing to a custom Log__c SObject a list of interesting things that happened during the course of execution. Dan Appleman's book 'Advanced Apex Programming' has a good debugging framework worth considering/adapting

Best Answer

Related Solutions

[SalesForce] Error when reading metadata: INVALID_TYPE: This type of metadata is not available for this organization

[SalesForce] Scheduled Apex not consistantly executing, sending emails

Related Topic