Unknown Exception thrown on Retrieval using API 50 against PRD Org - 617762167-31300 (-1792809135)

[Mike Eaton]

UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 617762167-31300 (-1792809135)

I created a new PRD Project and attempted to pull-down ALL component metadata as a pre-deployment backup just as I have down many times before without incident. However, this time I received the above-mentioned error message. This was run against an Org with Winter '21 Release using the API version 50.

1. Anyone else experience anything similar?
2. Any ideas on work-around?

I’ve attached a screenshot of the Error dialog. Please note that although the first set of error numbers differ in the screenshot, the error in parenthesis is the same (ie. -1792809135).

[Mike Eaton]

Work-around - Changed to API 49 and Retrieval succeeded.

[Mike Eaton]

Changed Priority to Major from Blocker since Work-around available.

[Scott Wells]

Mike, unfortunately GACKs like this are server-side errors in the Salesforce servers and are opaque to callers. I would encourage you to try to reproduce it via the Salesforce CLI by running the exact same retrieval operation and then, assuming you can reproduce it, log a case with Salesforce...or if you know someone who works there, e.g., some of the folks on the GDS group, ping them for more info.

[Scott Wells]

I'm going to resolve this assuming this is reproducible via the command-line and not an IC issue, but I'm happy to continue discussing how to get good diagnostic info that you can provide to Salesforce since it's obviously something introduced with the latest platform release.

[Scott Wells]

I've heard about this now from two other folks with the following distinct GACKs:

• 586142602-30233 (-1792809135)
• 834363887-91233 (-1792809135)

I can't remember how to decode these GACKs, but in all cases the parenthesized portion seems to be the same so hopefully they're all instances of the exact same underlying issue.

[Scott Wells]

UPDATE: I have received the following response from Salesforce about this:

Looks like that gack id is linked to W-8244571 and related to CustomIndex metadata? That is as much information as I have on it. It is currently a P2 with no scheduled build. If you want it expedited, the customers would need to file cases.

If this is affecting you, please log a support case with Salesforce referencing W-8244571 and your specific org/instance IDs as well as the GACK details.

=== ORIGINAL INFO ===

I've reported this to Salesforce. Reopening the issue until I get some guidance from them on when/whether it will be addressed, and also to raise visibility with end users who also experience this issue.

NOTE: If you've had this issue, please include the exact reported error ID similar to the one found in the issue subject. That will help Salesforce with diagnostics.

NOTE: A viable workaround seems to be changing the connection API version to 49.0. This is done in the connection manager settings for for native connections and in the sfdx-project.json file for SFDX-based connections.

[Scott Wells]

Issue #1762 was marked as a duplicate of this issue.

[Scott Wells]

Issue #1767 was marked as a duplicate of this issue.

[Scott Wells]

Issue tracker grooming. If this is still an issue, please feel free to reopen, ideally with a concrete reproduction scenario.