I refreshed a Developer Sandbox, and almost 24 hours it is still "pending". Is this normal? Are there any actions I can take to speed up the process? When I created the Sandbox it took barely more than 10 minutes to create.
Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It only takes a minute to sign up.Sign up to join this community
A status of Pending means, the sandbox refresh still hasn't started because other people's sandbox refresh requests are ahead of your request in the queue. Therefore, Salesforce doesn't provide SLA time. There's nothing much you can do but wait (indefinitely). Yes it is true that sometimes it can range from seconds to days to get to the front of this queue.
After your request reaches the front of the queue, the status would change from Pending to Processing and then to Ready for activation. Just for the sake of completeness, after you click the Activate link, the status would change to Activating and then to Created.
Since it is a developer sandbox, I'd not worry after crossing the Pending status. It should be fairly quick during the Processing status. There is no data to be copied, except for Custom Settings data. There are no slow queues and no fast queues for developer sandboxes - those are only for full sandboxes.
Related question: What is the maximum time taken for the refresh of a full-copy sandbox?
It depends on the number of customizations, data size, numbers of objects and configuration choices if you are having a full copy of your production. It also depends on server load. Bare in mind that sandboxes refreshes are queued. I read somewhere that there are two types. Slow queue and fast queue. If you are copying a large data source then you are listed on the slow queue. If it's small size data then you are on the fast queue. So to answer your question. Refresh time varies on the size of data etc of copying and the server load