Metadata type(s)
​affected

Gack error(s)

Cause and resolution (if known)

Apex class

(-493896994)

Update 27 June 2023: Salesforce confirmed that this error type was associated with a a bug. The bug fix should have been released in patch 244.12, which was scheduled for 10th of July 2023 (Safe Harbor).

Bulk API batch size is too large

(-1748883593)

This ID is likely surfaced when the Bulk API batch size is too large on a data deployment. We believe lowering the batch size in the settings can help work round this GACK code.

Document

(-547594032)

This ID is likely caused by the hitting limits of either deploying 10,000 files at once or having a zip larger than 39 MB.

Document,
​Email Template or Custom Metadata

(-673032061)

This ID has been surfaced with two causes that we know of:

EmailMessage

(-416219900)

This is related to a known Salesforce issue. Further details on root cause and resolution can be found here.
​
​Note: Gearset has a workaround for this issue if it happens in a Backup job. We are able to exclude the problem FromId field from the affected Backup job. It should help with getting your Backup job up and running, while Salesforce investigates and works on a fix.

Email Template or Email Alert

(-28317623)

This ID is likely caused by the hitting limits of either deploying 10,000 files at once or having a zip larger than 39MB.

FlexiPage

(-84759894)

This error may surface during a validation against a Salesforce org when API version 59 is used. Unknown cause at this time.

Flow

(-1177419986)

This code likely means that there is a missing required input parameter for a flow.

Flow

(553809687)

We suspect this issue could have been related to a custom built Apex invocable action (e.g. custom-built Apex class exposed for use in Flow metadata).

Layout

(-776149881)

The error was related to Layout metadata type. We observed that all Layout components that failed the validation were dependent on Quick action metadata type - at this point it's unclear if this is relevant to the error.

Milestone

(-465392833)

This ID is likely surfaced when a non-ASCII character has been used in the metadata or object name, or there is a missing character causing a parse error.
​

Can be caused by Apex code, and has been known to have been caused by an extra 'or missing'.

Permission Set Group

(-534360317)

This is caused by a Salesforce Summer '23 release.
​
Salesforce explains in their Known Issues that currently there is no workaround for this issue, and "in order to avoid any problems, double check that permission sets match between users in your sandbox and production environments."

Service Channel

(-545111196)

Error surfaced when validating a PR in Gearset Pipelines with caseChannel added to Delta CI deployment package.
​
​Possible root cause
User enabled Languages in the Second Priority Routing, which were not yet enabled in the Case Language field. Upon inspecting XML of the failing caseChannel component (caseChannel), these entries were appearing as:
​<serviceChannelFieldPriorities>
<priority>1</priority>
<value xsi:nil="true" />
</serviceChannelFieldPriorities>

While the third line <value xsi:nil="true"/> should have had a language value instead.
​
​Resolution
Removing these 4 lines of code rom caseChannel XML file helped to resolve the issue.

Service Report

(-1481549251)

Error surfaced during backing up client's Salesforce org. Unknown cause at this time.
​
The fields for ServiceReport object that Gearset requested when error was returned were:
​Id, IsDeleted, ServiceReportNumber, CreatedDate, CreatedById, LastModifiedDate, LastModifiedById, SystemModstamp, ParentId, ContentVersionDocumentId, DocumentName, DocumentContentType, DocumentLength, Template, ServiceReportLanguage, IsSigned, and Status.

Standard Value Set Translation

(-1201527775)

Unknown cause, but error was related to Standard Value Set Translation metadata type when this occurred.

Salesforce suggests a couple of options to try and resolve the issue:

Unsupported Group Type

(-693245406)

Unknown cause at this time, however the Salesforce API returns an issue regarding Contact_Centre_Group.

Unexpected error while processing BULK-API

(-820934765)

Failure is due to objects having different owners. For this code, group the knowledge articles by owner and break up the deployment.

Metadata type(s)
​affected

Gack error(s)

Cause and resolution (if known)

Apex class

(1566163925)

Unknown cause at this time, however it may have been related to unfinished code in one of the Apex classes.

Approval Process

(1169783681)

The error was related to ApprovalProcess metadata type components and the Case Custom object. Error occurred in a CI job.
Unknown cause at this time.

Call center

(1266517447)

Confirmed by Salesforce Support that this error is related to Call center metadata type. Gearset's recommendation is to exclude this metadata type from the filter if it continues causing an issue.

Content Asset

(1369604864), (1988552325), or (-186337334)

Unknown cause at this time. However, these three error IDs were related to the ContentAsset metadata type when the issues occurred.

Content Documents

(1140994461)

This is caused due to an invalid file type in ContentDocuments where the FileType is not known. This is known to occur when converting Attachments to ContentDocuments using this tool which doesn't support some file types.

Custom Field

(776095663)

The error was related to CustomField metadata - it was a changed picklist field retrieved from the source that errored on the validation.

Dashboard

(407174650)

The error was reported by a customer who was deploying dashboards. Including images led to fatal errors in the deployments.

Solution: Remove images from the dashboards during the deployment process, promote the dashboards without images, and manually add the images in the environment.

Document Template

(547557641)

Programmer Error: transaction committed or rolled back while performing api save object: DocumentTemplateContentDoc. The error message gets thrown when attempting to deploy the doc template manually.

Email Templates

(1214156259)

This is most likely due to private email templates with Modify All data permission unticked.

Flow

​(886823606)

This error is encountered on deployment when there is a referenced component that is missing or isn't installed in the target org. This could be a package that is being used in the Flow.

Flow

(2088258282)

This error was related specifically to Flow metadata type. Unknown cause at this time.
​
​Additional context on investigated use case:
Flow's status was Active in the source (Git branch), and the comparison in Gearset was run on API v 59, while the API version of the affected Flow was v60 (in Flow's XML file).
​

Workaround: The recommendation is to run the comparison in our app using API version 60 or higher to see if that resolves the error.

Lookup fields on Lightning pages

(1090241698)

It is a know Salesforce issue.
​
​Workaround:
If a lookup field on an object, points to an object that is not on the list of all supported ui-api objects this error will happen. If the offending field is removed from the object the error will no longer appear when editing or deploying lightning record pages.

Navigation Menu

(1248150380) and (1229852312)

These errors were related to the Navigation Menu metadata type when they occurred.
Unknown cause at this time.
​
The error (1229852312) was specifically related to the retrieval of Navigation Menu.

Omnistudio

(-2021970420) or (-320747095)

This error occurs when Omnistudio components are deployed alongside Salesforce components.
​
​Resolution: To avoid deployment errors, Salesforce recommends deploying OmniStudio components separately from setup-related (non-OmniStudio) objects.
More info in Salesforce documentation:
​Deploying OmniStudio Components with Other Objects Causes an Exception

Picklist Value

(1042929838)

This is caused by a picklist value that is no longer active on the target. Either remove the picklist value from the deployment, or activate it on the target org.

Picklist Value

(1086055316)

The picklist field throwing the error was marked for Field History Tracking on the object in the source org. However, the destination org was already at its maximum 20 out of 20 Fields for Field History Tracking.

Report Type

(2097016231)

Seems to be linked to the activation and deactivation of Sales Engagement studio. Causing report types to be associated with that.

Report Type

(-1780968743)

Error did occur on a package validation to a Salesforce org. The issue was related to specific ReportType metadata components.
​
​Solution: Excluding failing ReportType components from the metadata filer (of a CI job) resulted in successful validation, therefore it may not be required to exclude the entire ReportType metadata type from the filter if you know which reports are affected by the error.

User Access Policy

(278592139)

This error is encountered when user criteria is defined within a group.
​
This is a known Salesforce issue with no workaround proposed by Salesforce.

The solution would be to edit the User Access Policies in Salesforce to remove the group-based criteria before deploying.

Validation of test classes for orgs on UM3 instance

(-373587910)

This error may affect deployments of metadata for some orgs residing on UM3 instance. It is a known Salesforce issue affecting Sandbox > Sandbox, or Sandbox > Prod deployments.
​
​Workaround proposed by Salesforce:
​"The customers can raise a case with support to disable test class validation perm during deployment."
​
We've also seen a Gack error with reference (-373587910) surface on a Gearset user's backup job. It is recommended to contact Salesforce support to confirm the root cause of the issue.

Object affected

Gack error

Possible cause and resolution (if known)

Knowledge__kav

(-102717140)

We've seen this error during a deployment of some knowledge article records that had inactive users set as their Owner. Since Salesforce does not allow records to be created with inactive Owners, the deployment failed when attempting to assign those users.

Excluding or skipping the OwnerId field from the deployment configuration made the deployment successful.