You are here:
Troubleshooting Tips for Reporting Snapshots
The Run History section of a reporting snapshot detail page displays if a reporting snapshot ran successfully or not. When a reporting snapshot fails during a scheduled run, the failure is noted in the Result column. To view the details of a run, click the date and time of the run in the Run Start Time column.
Required Editions
Important Where possible, we changed noninclusive terms to align with our
company value of Equality. We maintained certain terms to avoid any effect on
customer implementations.
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions |
- If the Total Row Number is blank, the run failed before the report was completed (for example, the report was invalid or the running user is inactive).
- When a reporting snapshot runs, it can add up to 2000 new records to the target object. If there are more than 2000 new records, the additional records are not recorded, and the notification indicates that some rows failed.
- The details of a failed run are available on the Row Failures related list for 14 days before they are automatically deleted. You can't retrieve details about row failures from the Recycle Bin.
- If you have a unique field in the target object, and records in the report have more than one of the same value in the column mapped to that unique field, duplicate records are not added. The run history indicates when records are not added to the reporting snapshot.
- If field mappings failed, the snapshot still runs, but the run history shows that there was a partial error.
A reporting snapshot could fail during a scheduled run for a number of reasons. This table lists the errors a failed run may display and how the errors can help you troubleshoot the reporting snapshot so that it will run successfully.
| Error | Description |
|---|---|
| Running user does not have permission to run reports. | The user in the Running User field does not have the “Run Reports” or “Create and Customize Reports” permission. Choose a user with the appropriate permissions or enable the appropriate permissions for the running user. |
| Cannot run reporting snapshot because source report has been deleted. | The report in the Source Report field was deleted and no longer available to run. Choose another source report for your reporting snapshot or restore the deleted report from the Recycle Bin. |
| Running user does not have permission to access source report. | The user in the Running User field does not have access to the folder in which the source report is stored. Choose a user with access to the source report or provide the existing running user with access to the folder in which the source report is stored. |
| Source report definition is obsolete. | The report in the Source Report field references a custom or external object that is no longer available for reports or the relationships between the objects in the report have changed. |
| Source report definition is invalid. | The report in the Source Report field can't run because it contains invalid formulas or filter criteria. Update the report so that it can run without errors. |
| Running user does not have permission to access report type. | The user in the Running User field does not have permission to access a report type associated with the report in the Source Report field. Choose a running user that has the correct permissions or provide the existing running user with the appropriate permissions. |
| Source report must be tabular. | The report in the Source Report field is no longer in tabular format. Choose a new source report or update the existing source report's format to tabular. |
| Source report last saved with details hidden on report results. | The report in the Source Report field was saved with its details hidden. To display the details of the source report, view the report, click the Show Details button, and save the report. |
| Target object has been deleted or is inaccessible to running user. | The custom object in the Target Object field has been deleted or the user in the Running User field does not have permission to access the target object. Restore the deleted custom object, choose a new target object, or provide the existing running user with “Create” permissions to the custom object in the Target Object field. Note that if the custom object's status is In Development, the running user must have the “Customize Application” permission to access the target object. |
| Running user does not have permission to edit target object. | The user in the Running User field does not have “Create” permissions on the custom object in the Target Object field. Choose a running user that has such permissions or provide the existing running user with “Create” permissions to the custom object in the Target Object field. |
| Target object must not be a detail object in a master-detail relationship. | The custom object in the Target Object field is a detail object in a master-detail relationship, meaning that a master object controls certain behaviors on the target object's records. Choose a target object that is not included in a master-detail relationship. |
| Target object must not be included in a workflow. | The custom object in the Target Object field is included in a workflow. Choose a target object that is not included in a workflow. |
| Target object must not include an insert trigger. | An Apex trigger runs when new records are created for the custom object in the Target Object field. Remove the Apex trigger or choose a target object for which an Apex trigger does not run when new records are created. |
| Target object must not include validation rules. | The custom object in the Target Object field contains validation rules. Choose a target object that does not contain validation rules or delete validation rules from the existing target object. |
| Running user is inactive. | The user in the Running User field is no longer active. Choose an active user. |
| One or more required fields on the target object are not mapped. | One or more required fields on the target object are not mapped. Map all required fields on the target object to fields on the source report. |
| Source report contains too many fields, has a formula field with too many functions, or contains too many criteria. | The report in the Source Report field contains too many fields, criteria, or functions within a formula field. Remove any unnecessary fields, criteria and functions within formula fields from the source report. |
| Source report cannot have more than 100 selected columns. | The report in the Source Report field contains more than 100 fields. Remove any unnecessary fields from the source report. |
| Target object cannot have more than 100 custom fields. | The custom object in the Target Object field contains more than 100 custom fields. Remove any unnecessary fields from the target object. |
| Your report exceeded the time limit for processing. | The report in the Source Report field may contain too much data to process. Reduce the amount of data the report processes when running by limiting the report's date range and remove any unnecessary fields from the source report. |
| This Reporting Snapshot Unique Name already exists. Please choose a unique name. | The new snapshot you are trying to create has the same unique name as that of a existing snapshot. |
| A summary field did not return a valid number. | A summary field in the results has not returned a valid number. For example, the field may have attempted to divide by 0. Check your formulas and test for 0 and “null” in calculations if they appear in your data. |
| There is a problem with this reporting snapshot. The source report format was changed from tabular to summary. The field mappings in the reporting snapshot are no longer correct. You can change the report format back to tabular or update the field mappings in the snapshot definition. | The source report format was changed from tabular to summary, which made the field mappings in the reporting snapshot incorrect. To fix this error, either change the report format back to tabular or update the field mappings in the snapshot definition. This error only applies to reporting snapshots with summary reports. |
| There is a problem with this reporting snapshot. Source report must be tabular or summary. | The source report format must be either tabular or summary. Reports grouped by rows and columns (matrix) can't be used with reporting snapshots. |
| The grouping level you specified in the reporting snapshot is no longer valid. The running user may no longer have access to that field, the grouping level may have been removed from the source report, or the grouping level was never set. | This error may result when the running user no longer has access to the field specified in the grouping level, or the grouping level was removed from the source report or was never set. This error only applies to reporting snapshots with summary reports. Make sure the running user has access to all necessary fields. |
| A record cannot contain multiple fields with different currency codes. Verify that all currency fields in the source report rows have the same currency code. | This error message is expected when records within the source report for a reporting snapshot contain multiple currencies. To prevent this snapshot failure, replace the Amount field with the Amount Converted field. To track a currency field, always use the converted version of a field. |
| Data discrepancy in reporting snapshots using date/time fields after a Daylight Saving Time (DST) change. | Salesforce stores date/time values in GMT and converts them to the running user’s time zone for display and reporting. When Daylight Saving Time (DST) begins or ends, date/time values can shift by one hour. This shift causes reporting snapshots to appear inconsistent over time. To ensure consistency in future snapshots, use a running user with a time zone that does not observe daylight saving time. |
See Also
Did this article solve your issue?
Let us know so we can improve!
