5

Were you able to deploy External Credential, or have you left it out as a manual step?

We currently try to deploy a package with a Named Credential, using External Credential (new on Winter'23) with API version 56.0 using SFDX, and we keep getting GACKs. This pipeline's first step is running deployment validation (--checkonly).

The current GACK is An unexpected error occurred. Please include this ErrorId if you contact support: 819874669-15988 (2056426840).

I have also checked the Metadata Coverage Report for v56 and the Salesforce CLI Release Notes (it since 7.173.0 - October).

7
  • 1
    Based on Salesforce backend logs, the stacktrace 2056426840 points to java.lang.ClassCastException: class system.user.permission.CustomPermissionSetObject cannot be cast to class system.user.permission.PermissionSetObject I can see this was also reported on Github and tagged to internal bug # W-12075756 Dec 19, 2022 at 9:53
  • 1
    I am following up internally and will let you know as I have more details. Thanks Dec 20, 2022 at 9:44
  • 1
    Hello @Swetha: thanks for following up internally, were you able to get more insights that you could share? Jan 23, 2023 at 10:39
  • 1
    Hey Swetha, no worries, it is fair enough. Would 242 mean Spring'23 release? Jan 30, 2023 at 11:51
  • 1
    That is correct. 242 is Spring'23 Jan 31, 2023 at 8:24

1 Answer 1

1

As mentioned in the comments, the stacktrace ID (2056426840) corresponds to java.lang.ClassCastException: class system.user.permission.CustomPermissionSetObject cannot be cast to class system.user.permission.PermissionSetObject based on the Salesforce backend logs and this was also reported on Github by another user.

Upon following up with the concerned Salesforce product development team, the issue has been fixed as part of #W-12361127 and the fix has been rolled out last week in the Spring'23 release patch(242)

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .