Loading
Prepare for Email to Become the Default Login ExperienceRead More
Set Up and Maintain Your Salesforce Organization
Common Errors and Warnings in the Archive App

You are here:

  1. Salesforce Help
  2. Docs
  3. Set Up and Maintain Your Salesforce Organization

Common Errors and Warnings in the Archive App

Errors and warnings that occur when using the Archive app, and how to solve them.

Error Name Error Code Reason Solution
Blocked Domain This site can't be reached. app1.archive.owndata.com unexpectedly closed the connection. A firewall is blocking owndata.com domain and failing the re-authentication process. If this message appears during the onboarding or re-authenticating process, contact Salesforce Support to verify whether Allowlisting is required to access the Own domain.
Bulk Delete Process Halted Bulk Delete Process Halted The process failed as part of the bulk delete process.

Update these configuration settings.

  • Deselect the hard delete option in the Archive Settings.
  • If one of the children failed to delete because of the lookup relation, if possible, deselect the lookup relation.
Connection Reset by Peer Connection Aborted WARNING: Connection Reset by Peer Connection Aborted Likely temporary connection issues with Salesforce. Archive runs and re-runs the policy as scheduled on a daily, weekly, or monthly basis but gets the same error.

Attempt one of these solutions.

  • Rerun the operation.
  • Wait for the next archive policy run.
  • Reduce the number of lookups in the archive policy.
  • If it includes lookup children, split the archive policy. Add other Archive policies where the root objects are the lookup children.
  • If these previous methods fail to resolve the error, contact Salesforce Support. An internal optimization that reduces the probability of getting this error from Salesforce.
Custom Trigger Error Class.TriggerName Custom triggers have been set up and are causing Archive or Unarchive errors.

Attempt one of these solutions.

  • Disable the trigger during the Archive or Unarchive action.
  • If the custom triggers were implemented with byPassValidationAssign, assign the Integration User bypass triggers.
  • Amend the custom trigger logic so that Archive can bypass it.
Delete Operation Too Large DELETE_OPERATION_TOO_LARGE: Cascade dereferencing too many records This issue is commonly the result of a large number of records being associated with the deleted record through a master-detail or lookup relationship. To resolve record deletion performance issues, identify and delete related records, and empty them from the Recycle Bin. For more information, see Error 'Delete Operation Too Large' or too slow when you delete records.
Enable Email Drafts for Cases Not Enabled INVALID_OPERATION Enable Email Drafts for Cases feature isn't enabled. To insert the email message, add the option to enable Draft emails. For more information, see Enable Email Drafts for Cases.
Field Custom Validation Exception—Bad Restricted Picklist Value FIELD_CUSTOM_VALIDATION_EXCEPTION: Bad value for restricted picklist field

When unarchiving, Salesforce can encounter data validations such as validation rules, restricted picklist, and duplicate rules. In addition to this error message, you can receive one of these messages.

  • Validation rule message
  • sf_delete_error_message_object: status_code: FIELD_CUSTOM_VALIDATION_EXCEPTION
  • error_message: bad value for restricted picklist field: Closed Lost - Account Merged; Originating Class: UpdateOpportunityBeforeMergeAccount
  • object_id: 001C000001CVN1sIAH

Attempt one of these solutions.

  • Deselect restricted picklist value and add a new value.
  • Deactivate the new picklist value and replace it with an existing picklist value.
Integrated User Has Limited Permissions The integration user has limited permissions The permission to query storage details using the tooling API is missing.

Add these permissions.

  • API enabled
  • Manage Multi-Factor Authentication in API
  • View Setup and Configuration
Insufficient Access on Cross-Reference Entity INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY: insufficient access rights on cross-reference id: [different record id] Unarchiving requires a reference to the above record, and the Integration User can't access it.

Verify whether the referenced record exists. If the record exists, verify the Integration User's permissions to the record. Verify the Integration User has the ModifyAllData permission.

If the error persists, contact Salesforce Support.
Invalid Record ID Invalid Record ID The External Lookup Relationship reference field isn't supported when expanding the object record page layout to view records via the Archive component or Archive Search. Remove the External Lookup Relationship field from the component or Archive Search fields configuration.
Modify All Permission Required WARNING: Root object of type A Modify All permission is missing, or Salesforce encountered internal issues with references.

Verify that the Integration User has Modify All permission on the relevant record type.

If the error persists, contact Salesforce Support.
OAuth Access Blocked

One or more of these symptoms occur:

  • Archive dashboard doesn't load or shows access errors
  • Connected App shows blocked actions in OAuth Usage
  • Can't access Archive after updating permission sets
 Permission changes can invalidate OAuth tokens. Connected App policies may block access.

Attempt these solutions in order.

  • In Setup, go to Connected Apps > Connected Apps OAuth Usage.
  • In the Search field, enter Archive, then select your Archive app.
  • Verify that all actions associated with the app are unblocked. If you see blocked actions, select them and click Unblock.
  • Review the Connected App policies and verify that the System Administrator and Integration User profiles are listed under Permitted Users. If these profiles are missing, add them to the permitted users list.
  • From the App Launcher, open Archive and verify that the dashboard loads without errors.
Record Failed to Delete Unknown_Exception The record failed to delete. No Salesforce error due to Salesforce unknown exception.

Attempt one of these solutions.

  • Reduce the archive policy limit to a smaller number and rerun the policy.
  • Delete one of the IDs manually.
  • If the error persists, contact Salesforce Support.
Record No Longer Exists Unable to unarchive object with original Salesforce Id:01a2B345673rkcaABC. Reference IDs not found: [list of records] The record you're trying to unarchive references a record that's no longer in Salesforce or in Archive. The reference field is obj.field.

Unarchive by disconnecting the root-child relationship.

After you export and download the record, locate the record ID in the CSV file.

Nullify the field, save your changes, and import the file to Salesforce via an ELT tool.

Then purge the record from the Archive database.
Related Tab Error Error Show related object details operation encountered an error, contact support and provide them with this Error code - 10085#10087#10142#10178 Clicking the Related tab in Archive Search triggers an error. Verify the Archive Settings under Search and Component Layout. Remove any non-indexed fields from the selected fields.
Revoked Authentication Token Get Organization Storage Statistics operation encountered an error, please contact support and provide them with this Error code - 10076#10035#10200. The authentication token has been revoked or IP access is blocked to the Archive backend servers.

Attempt one of these solutions.

Secure Static Resources for Lightning Components Error Error: lightning/platformResourceLoader encountered an error loading. The Archive page fails to load.

Secure Static Resources for Lightning Components is enabled, which can happen when you:

  • Download execution details from Activities tab.
  • Load Archive Dashboard custom components in the home page.
  • Load Archive Search.
  • Reconfigure the Region.

Contact Salesforce Support and request to deactivate these Secure Static Resources for Lightning components.

  • AuraSecStaticResCRUCPerm—Permission to hide Aura Secure Static Resources release update on new orgs.
  • AuraSecStaticResCRUCPref—Org preference that enables Aura Secure Static Resources release update.
Too Many Failures Too_many_failures: failures limit crossed A query failed to archive records due to a trigger, dependency, or validation rule.

Disable the trigger or validation rule that inhibits the policy from deleting this record.

If this error is due to a dependency, archive the referenced dependency before you archive the record.
Unarchive Apex Request Rate Exceeded Error Message: {"error_code": "VALIDATION _ERROR", "error_message": "Exceeded maximum Unarchive SDK request rate."} You sent too many requests within the given time. Apex supports up to 50 Unarchive requests per hour. Wait and try again later.
Wrong Archived Root Record Referenced Unarchive Failed: The record can't be unarchived because it references another archived root record. To resolve this issue, adjust the Unarchive Reference setting and try again. Unarchive failed because the record references another archived root record. Update the Unarchive Reference setting to permit unarchiving of records with archived references.
Wrong Reference ID Unable to unarchive object with original Salesforce Id: 01a2B345673rkcaABC Reference IDs currently archived: [list of archived records] The record you're trying to unarchive references another archived record. The missing records are listed in the the Failed Records column of a CSV file that you can download from the Activities tab.

Attempt one of these solutions.

  • Unarchive the root record before unarchiving the child record. For more information, see Enable Unarchive When Parent Record Archived.
  • Unarchive by disconnecting the root-child relationship.

    After you export and download the record, locate the record ID in the CSV file.

    Nullify the field, save your changes, and import the file to Salesforce via an ELT tool.

    Then purge the record from the Archive database.
Policy Preview No Records Found No records matching your policy criteria were found in the preview sample. All records were filtered by policy constraints, such as ContentDocument owner requirements. The policy preview filtered all candidate records due to policy constraints. This can happen when your SOQL query returns records that don't meet the policy's filtering requirements.

Attempt one of these solutions.

  • Refine your SOQL query to target records linked to the selected parent object.
  • Run the full policy to see actual results instead of relying on the preview sample.
 
Loading
Salesforce Help | Article