When retrieving full set of metadata (all items checked) from source org, I get this error consistently, even from different orgs

Scott Wells repo owner

changed status to open

Hi. This is the relevant part:

UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 1234567890-123456 (-123456789)

That is an internal server error on the Salesforce side of things, often called a GACK. Because these are opaque internal server errors, you typically either need to file a support case with Salesforce to get the underlying cause, or perhaps if you know someone at Salesforce with access to system logs, you can ask them for more details on the exact specified error ID.

The alternative is to try to isolate the specific metadata types/objects in the retrieve request which are resulting in this error, typically by process of elimination. Just either build up to the full retrieval request until it fails, or incrementally remove items from the request until it succeeds.

I will say that I do not think it's a good idea to try to retrieve all metadata from any org. In all cases, there is a specific subset of metadata that represents your customizations and extensions to the organization, and that should be all that you need to externalize. There are also some metadata types/objects that are reported by the Salesforce APIs but are not really valid for retrieval. They can either yield errors like this when trying to retrieve them, or they can yield similar errors after a successful retrieval when you try to deploy them, even back to the same org. I'd strongly recommend that you create a specific metadata subscription for what is needed by this project.

I apologize that I can't provide more information, but GACKs are opaque and can only really be identified clearly by Salesforce.

2023-12-22T15:24:05+00:00

Scott Wells repo owner

changed status to resolved

Resolving as this is a Salesforce internal error and is likely due to some subset of metadata types/objects specified in the retrieval request. If, after identifying the specific type(s)/object(s) that are causing the error, you determine that this is in fact some issue with how IC2 is sending its API retrieval request, feel free to reopen with those details.

2023-12-22T15:25:23+00:00

Kirk Orrick reporter

attached idea.log
attached open-telemetry-metrics.2023-12-22-09-57-49.csv

  <div class="preview-container wiki-content"><!-- loaded via ajax --></div>
  <div class="mask"></div>
</div>

</div> </form>

2023-12-22T16:38:11+00:00

Kirk Orrick reporter

Thanks. This worked previously. I wouldn’t normally download everything, but I wanted a backup in advance of a refresh. Thank you for looking.

2023-12-22T16:40:00+00:00

Scott Wells repo owner

Yeah, it’s hard to say given the completely opaque nature of these types of errors. But I’ve seen GACKs start suddenly, sometimes just due to seemingly small changes from Salesforce’s weekly maintenance patch releases. My guess is that if you distill the metadata subscription (and resulting retrieval request) down to the subset of metadata required for this project, you won’t see this error any longer.

2023-12-22T16:43:33+00:00

Comments (5)