Common Errors and Warnings in the Archive Managed Package

Warning Error Access denied for Archiver backend. Please contact support.

Reason: Salesforce is migrating your data from their private clouds to AWS public clouds.

Solution: Enable the Hyperforce settings by following the steps outlined in Update Archive Security Control for Hyperforce Customers.

Warning This site can't be reached. app1.archive.owndata.com unexpectedly closed the connection.

Reason: A firewall is blocking owndata.com domain and failing the re-authentication process.

Solution: If this message appears during the onboarding or re-authenticating process, contact your IT support to check if Allowlisting is required to access the Own domain.

Warning Bulk Delete Process Halted

Reason: The process failed as part of the bulk delete process.

Solution: Update configuration settings.

Warning Connection Reset by Peer Connection Aborted

Reason: The issue may be due to temporary connection issues with Salesforce. Archive tries to rerun but gets the same error. Archive runs the policy as scheduled (daily/weekly/monthly basis).

Solution:

Warning Class.TriggerName

Reason: Custom triggers have been set up and are causing Archive/Unarchive errors.

Solution 1: Disable the trigger during the Archive/Unarchive action.

Solution 2: If the custom triggers were implemented with byPassValidationAssign, assign the Authenticated User bypass triggers.

Solution 3: Amend the custom trigger logic so that Own Archive can bypass it.

Warning DELETE_OPERATION_TOO_LARGE: Cascade dereferencing too many records

Reason: 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.

Solution: To resolve record deletion performance issues, identify and delete related records, empty them from the recycle bin. See more in Salesforce under Error 'Delete Operation Too Large' or too slow when you delete records

Warning INVALID_OPERATION

Reason: Enable Email Drafts for Cases feature is not enabled.

Solution: To insert the email message, add the option to enable Draft emails. See more from Salesforce in Enable Email Drafts for Cases.

Warning App Feature Settings operation encountered an error, please contact support and provide them with the following Error code - 10094#10002#10001#10178

Reason: The security certificate associated with the installed Archive managed package has expired. This prevents the package from communicating securely with the Archive backend services.

Solution: Upgrade the Archive managed package to the latest available version. You can find the latest installation links in Access to Own from Salesforce Products .

Warning Failed to Load Query Builder

Reason 1: Refreshing a sandbox environment can cause errors because the Archive Console retains the old sandbox ID.

Solution: Re-onboard the refreshed sandbox by hiding the old entry and adding the sandbox again with its new org ID in the Archive Console.

Reason 2: The system attempts to fetch information from the org. If a response isn't received within 30 seconds, a timeout error occurs.

Solution: Retry the action, preferably at a later time.

Reason 3: Updates to permissions and permission sets can prevent the Archive product from accessing and managing the org data.

Solution: Review the permissions assigned to your Archive authenticated user.

Warning FIELD_CUSTOM_VALIDATION_EXCEPTION: Bad value for restricted picklist field

Reason: When unarchiving, Salesforce can encounter data validations such as validation rules, restricted picklist, and duplicate rules. In addition to this error message, you can see additional text with:

• 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
• sobject_id: 001C000001CVN1sIAH

Solution 1: Uncheck restricted picklist value and add a new value.

Solution 2:Deactivate the new picklist value and replace it with an existing picklist value.

Warning FIELD_CUSTOM_VALIDATION_EXCEPTION: You are not authorized to delete this email, sobject_id: None

Reason: When unarchiving, Salesforce can encounter data validations such as validation rules, restricted picklist, and duplicate rules. In addition to this error message, you can see additional text with Validation rule message and sf_delete_error_message_object: status_code.

Solution: Deactivate the validation rules.

Warning The integration user has limited permissions

Reason: The permission, granting access to query the storage details using the tooling API is missing.

Solution: Add one of these permissions.

• API enabled
• View setup and configuration and Multi-Factor Authentication
• Manage Multi-Factor Authentication in API

Warning Failed, Record is considered hot data because it was modified in the last 90 days.

Reason: Hot data is considered as any data that has been modified within the last 90 days. This is a protection mechanism that can be manually reconfigured from its default On state.

Solution: Disable hot data protection through Archive Setting > Archive > Salesforce Data Protection Period and re-run the policy.

Warning INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY:insufficient access rights on cross-reference id: [different record id]

Reason: Unarchiving requires a reference to the above record, and the authenticated user can't access it.

Solution:

Warning Invalid Record ID

Reason: The reference field External Lookup Relationship is not supported when expanding the object record page layout to view records via the Archive Widget or Archive Search.

Solution: Remove the field from the Archive Widget or Archive Search fields configuration.

Warning Root object of type <Parent Record Type> with Id <root Id> isn't archived because archive operation failed to read these children: record not found in Salesforce! It is recommended to ensure that the Archive Integration User has read permission for this object and has the Modify All permission.

For example: [(type: <Child Record Type>;IDs:<Child Ids>), <Possible another children types>

Reason:

• A Modify All permission is missing.
• Salesforce encountered internal issues with references.

Solution:

Warning Validate Query operation encountered an error.

Reason: New org or refreshed sandbox hasn't been fully configured.

Solution: Verify Archive is installed properly. For more information, see Verify Archive Package Installation and Functionality.

Warning This policy was created or edited from the Archive Console. You can't drill down or edit this policy from the Package.

Reason: From Archive Package 21, when a policy is created or edited from the Archive Console, it's no longer accessible from the Archive Package, except for the Run Now feature, if enabled.

Solution: Access the Archive policy from the Archive Console with Archive Package 21 and later installed.

Warning Unknown_Exception

Reason: The record failed to delete. No Salesforce error due to Salesforce unknown exception.

Solution:

Warning Unable to unarchive Sobject with original Salesforce Id:01a2B345673rkcaABC. Reference IDs not found:

Reason: 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 (API name).

Solution: Unarchive by disconnecting the parent/child relationship.

Warning Error Show related object details operation encountered an error, contact support and provide them with this Error code - 10085#10087#10142#10178

Reason: Clicking the Related tab in the Archive Search triggers an error.

Solution: Check the Archive Settings under Search and Widget Layout. Remove any non-indexed fields from the selected fields.

Warning Get Organization Storage Statistics operation encountered an error, please contact support and provide them with this Error code - 10076#10035#10200.

Reason: The authentication token has been revoked or IP access is blocked to the Archive backend servers.

Solution 1: Verify Archive is installed properly. For more information, see Verify Archive Package Installation and Functionality.

Solution 2: Review IP restrictions and ensure access to the Archive servers is allowed by reviewing the Own Regions and IP Addresses for Allowlisting.

Warning Error: lightning/platformResourceLoader encountered an error loading

The Archive page fails to load.

Reason: Secure Static Resources for Lightning Components is enabled.

This can happen when:

• Trying to download execution details from Activities tab.
• Loading Dashboard widgets in the Homepage.
• Loading the Archive Search.
• Trying to reconfigure the Region (applicable to package 18 and below).

Solution: Deactivate Secure Static Resources for Lightning Components.

Open a ticket with Salesforce Support to disable these components.

• Permission: Perm to hide Aura Secure Static Resources release update on new orgs (AuraSecStaticResCRUCPerm).
• Org Preference: Pref to enable Aura Secure Static Resources release update (AuraSecStaticResCRUCPref).

Warning Fail to insert/update policy Upsert failed. First exception on row 0; first error: STORAGE_LIMIT_EXCEEDED, storage limit exceeded: []

Reason: Your Salesforce environment is beyond its limits and no new records can be created.

Solution: Manually delete some records so that Archive can create the record for the archiving policy.

Warning Too_many_failures: failures limit crossed

Reason: A query has failed to archive records due to a trigger, dependency, or validation rule.

Solution: Disable the trigger or validation rule that's inhibiting the policy from deleting this record.

Note If the issue is due to dependency, Archive the referenced dependency first before you archive this record.

Warning Error Message: {"error_code": "VALIDATION _ERROR", "error_message":"Exceeded maximum Unarchive SDK request rate."}

Reason: This message indicates that you have sent too many requests within the given time. The SDK supports up to 50 Unarchive requests per hour.

Solution: Wait and try again later.

Warning 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.

Reason: Unarchive failed because the record references another archived root record.

Solution: To fix this, update the Unarchive Reference setting to allow unarchiving of records with archived references.

Warning Unable to unarchive sObject with original Salesforce Id: 01a2B345673rkcaABC Reference IDs already archived:

Reason: The record you are trying to unarchive references another archived record. The missing records are listed in the Activities tab, CSV file, under the Failed Records column.

Solution 1: Unarchive the parent before unarchiving the child record. See Unarchive from Archive Search or Archive Widget.

Solution #2: Unarchive by disconnecting the child/parent relationship.