Retrieve stuck on "Pending" - gives "Already disposed: Module" error message

[Baird Straughan]

Hi Scott,

I've waited about an hour for a retrieve to go through, and finally this error popped up:

Already disposed: Module: 'KSCGACopy sandbox' (disposed)

What's the solution here?

Thanks in advance

Baird

[Scott Wells]

Anytime that a retrieve (or deploy) is taking a long time, it's almost certainly due to server-side queueing. You can confirm that by enabling debug logging for Metadata Retrieval and Salesforce DX, reproducing the behavior, and looking at the resulting idea.log which will almost certainly show that the retrieval request has been submitted and IC is just polling the server for status. Moreover, that status will likely be reported as QUEUED, PENDING, or similar.

If that's in fact the case, you will need to log a support case with Salesforce, specifying your org and instance IDs so they can figure out why things are queued so badly.

If you don't see what I've described, feel free to attach or email the idea.log for review.

Regards,

Scott Wells

[Baird Straughan]

Hi, 

after 24 minutes the retrieve completed.

"Retrieved 12/12 components from KSCGACopy sandbox in 24 m 28 s 77 ms with status SUCCEEDED."

I'm glad this worked, but a little apprehensive that other code retrieves will take as long.

Baird

[Scott Wells]

Yeah, there's no good reason for a 12 component retrieval to take that long. I guarantee that it was stuck in queue and actually processing was seconds at most. If this behavior continues, please get a log as detailed in my previous response and, assuming you see the described behavior, log a support case with Salesforce so they can fix whatever is going on.

Regards,

Scott Wells