Just as with metadata deployments, you may sometimes run into deployment errors when moving records between orgs. This article gives a short guide on how to identify and resolve these errors.

Deployment status: continue on errors vs stop

When configuring a data deployment, you can specify what you'd like Gearset to do if it encounters any deployment errors. Which option you choose will impact how Gearset displays the overall deployment status.

Continue deploying remaining records

Gearset will attempt to deploy as many records as possible, regardless of errors. Any records that fail will be skipped.

With this option, you will see the deployment completed banner if Gearset is able to complete the planned deployment steps, regardless of how many records are deployed.

Stop deploying remaining records

As soon as Gearset hits a deployment error, the deployment will stop. Any remaining records will not be deployed.

With this option, you'll see the deployment failed banner if Gearset encounters any errors or was not able to deploy all of your records.

How are data deployment errors displayed?

If Gearset encounters any issues which stop it from moving records, you'll see a banner at the top of the deployment summary page.

Any steps with errors will give a description of the errors and provide more information on how to resolve them. For example, in the screenshot below there is an issue with duplicate values in the target org and a link to a support article which explains the issue in more detail. Some changes need to be made to the target's data to enable Gearset to deploy those records.

Identifying affected steps in the data deployment

Alongside the banner at the top of the page, any deployment steps that were affected by a deployment error will display additional information and automatically expand to make them easy to discover. 

For example, the issue with duplicates above affected the upsertstep on the account object. Only 1 of the 15 records selected for deployment were successfully created. The error message from Salesforce relating to the remaining 14 records, and their record IDs, are displayed at the bottom of the step.

If you set Gearset to stop on deployment errors, only the first step which encounters an issue will display the deployment errors. Subsequent steps which were not carried out will be marked as cancelled. 

Did this answer your question?