When deploying to Salesforce, common errors can occur, such as incorrect permissions, missing data, or other issues. To help users identify these issues before deployment, Gearset includes a data problem analyzer which will scan the restore/deployment plan to identify any problems that could prevent a successful restore or deployment.

There are two type of problems that can be flagged by the data problem analyzer: Those with fixes, and those requiring manual intervention.

When Gearset can identify a problem with an automatic fix, such as missing parent records from the restoration, it will provide a fix button to add the missing parent record automatically.

For example, if a child record is present in the restoration, but its parent record does not exist in the org or the restoration, Gearset can add the missing parent record to the restore/deployment automatically. An example here is a user trying to restore a deleted Opportunity that has a reference to a deleted parent Account record, however the deleted Account record was not initially included in the restoration. This restoration would typically fail, but Gearset gives you the option to be able to fix this by adding in the deleted Account.

There are some problems that Gearset will be unable to provide automatic fixes for, such as permission issues, or missing data that is not in backup/source org. In this case, Gearset will inform you that the problem requires manual intervention, and provide a link to documentation to help you fix the problem.

An example of a problem that Gearset is unable to automatically fix is when there is a reference to missing RecordType in the deployment which is missing from the backup.

In some cases, users may wish to ignore the problem analysis and proceed with the restore process. Gearset allows users to skip the analysis while it is still running, and after it completes, they can continue by pressing "Preview restore" and then selecting "Preview restore (Not recommended)" on the warning popup that appears. It is important to note that this should only be done when users are confident that the restore process will not encounter any issues that the data problem analyzer would have flagged.