When an execution fails, check that Heroku is properly installed and connected. Then run a report or query to identify the failed records and find possible next steps to resolve the error.
Required Editions
| Available in: all editions |
| User Permissions Needed | |
|---|---|
| To resolve failed executions: | ModifyAllData and PrivacyCenter |
When an execution fails, first confirm that Heroku is properly installed and connected. Make sure that your org is onboarded and that Heroku is installed with a member of the Privacy Center production team. If your org is correctly configured with Heroku, either run a report on the object or run a query in the Developer Console. To identify the records that failed during execution, look for any instance where the Last Modified Date and the date of the execution aren’t equal.
After identifying which records failed, check the Run Logs or Apex jobs for details on the cause of the failure, and then resolve any errors. To check that the errors are resolved, first deactivate and then reactivate the policy to schedule the policy again. Then, from the Retention Policies page, find the name of your policy and click Run. You can also make your new execution more specific by applying a Data Filter to the Policy that matches the failed records. Although the specific filters vary depending on the use case, the same Last Modified Date is a good place to start.