If your Data Backup job includes objects with associated binary files, you may occasionally see a message on the job card indicating that some files weren't backed up:
Clicking View details will open a modal. This modal provides a tabular view of the objects and the number of binary files that Gearset was unable to download from Salesforce:
How can I find out the specific files?
To pinpoint the exact files that weren't backed up, follow these steps:
From the modal, click the Run ID link. This takes you to the summary page for that specific backup run.
On the run summary page, find the object you're interested in (for example,
ContentVersion) and click View records.
You'll now be on the object details page, showing all records for that object within the run. To see only the records Gearset couldn't download, apply a field filter. Set the filter on the relevant field that holds the binary file data to
failedToFetch.For
ContentVersion, you'd filter the VersionData field for values equal tofailedToFetch.
The resulting records are the ones that Gearset was unable to download during the run.
Which field should I filter by for other objects?
The field you need to filter by depends on the object. Here's a quick guide for the most common objects:
Object name | Field to filter by | Value to filter by |
Attachment | Body | failedToFetch |
ContentVersion | VersionData | failedToFetch |
EmailMessage | HtmlBody | failedToFetch-HtmlBody |
EmailMessage | TextBody | failedToFetch-TextBody |
Document | Body | failedToFetch |
StaticResource | Body | failedToFetch |
Why weren't these files backed up?
Files might fail to back up for a few common reasons:
Permissions issues: The Salesforce user Gearset uses may not have sufficient permissions to access and download certain binary files within your org.
File corruption: The binary files themselves might be corrupted or malformed within Salesforce, preventing Gearset from downloading them successfully.
Salesforce internal limits: Less commonly, Salesforce might impose temporary limits on file downloads, or experience momentary internal issues.
If you consistently see certain files or objects failing, it's worth reviewing the permissions of your Gearset Salesforce user and inspecting the problematic files directly in Salesforce.