OwnBackup for general Salesforce errors and warnings (2023)

Invalid credentials: the service cannot connect to Salesforce

• Reason 1:Connected blocked OAuth application
• Solution:
  • In Salesforce--> Setup > Apps > Connected Apps > Connected Apps OAuth Usage page.
  • Make sure the Lock button next to OwnBackup for Salesforce (data service) or (metadata service) is not selected.
• Reason 2:Salesforce IP Restrictions – IP restrictions are set in Salesforce and IP addresses of OwnBackup applications must be whitelisted in Salesforce.
• Solution:Check the relevantOwnBackup IP addressesthey are whitelisted at the organization level and profile level of the authenticated user assigned to the service.
• Reason 3:Custom Domain – When a custom domain is enabled and defined as the only way to log in to your organization on the Salesforce login screen.
• Solution:Select the Custom Domain option before entering the username/password to authenticate the service. Read more aboutcustom domainConfiguration in Salesforce.

Unauthorized User / INSUFICIENT_ACCESS - Insufficient access rights to the locator ID.

• Reason 1:No "Change All Data" permission.
• Solution:Make sure the authenticated user has the ModifyAllData permission. Also verify that the authenticated user has proper access to the specified object and all referenced objects.
• Reason 2:Sandbox Reauthentication: A sandbox environment was recently upgraded and now the backups are failing.
• Solution:
  • Select the failed sandbox service, and then select the "Re-authenticate service" option.
  • Log in with the username/password of the authenticated user. If you have a custom domain, be sure to use it before entering your credentials.
  • Upon completion, a new sandbox service panel will appear on the backup page.
  • If the service does not appear on the backup page, make sure the service does not appear on the Archived tab in OwnBackup. You can unarchive it directly from the Archive page to Active Backup status.

Sorry, this Salesforce org is already taken.

• Reason:This Salesforce org is already connected as a service to another active OwnBackup user account.
• Solution:If you can't find the owner of this OwnBackup account or you think this message is incorrect, please contact support.

Invalid query locator

• Reason 1:The user is requesting too many threads (maximum 10) at any given time.
• Solution:
  • Assign an authenticated user to OwnBackup and avoid using other requests from the current authenticated user for other Salesforce requests.
  • Consider dedicated separate authenticated users for OwnBackup data and metadata services in the same Salesforce org.
  • Salesforce "INVALID_QUERY_LOCATOR" error article link.
• Reason 2:A sequence request initiated by OwnBackup has expired in Salesforce and is no longer responding to further queries.
• Solution:These warnings are temporary and do not require any action and should resolve on their own.

Could not process request: OPERATION TOO LARGE

• Reason:No View All Data and Modify All Data permissions and the query exceeded 100,000 unique IDs
• Solution:Make sure the authenticated user has ViewAllData and ModifyAllData permissions. Also verify that the authenticated user has proper access to the specified object and all referenced objects.

bad_query

• Reason:No "View All Data" and "Modify All Data" permissions
• Solution:Make sure the authenticated user has ViewAllData and ModifyAllData permissions. Also verify that the authenticated user has proper access to the specified object and all referenced objects.

File download limit reached/API download limit reached

• Reason:Some of the indexed files, attachments, content documents, and content versions were not downloaded in the backups.
• Solution:
  • The default limit is set at 5,000 files per backup, which can be increased to 300,000 files. WatchThis articlefor more information on setting limits.
  • Check API consumption in Salesforce: Setup > System Overview > API Requirements. Check the maximum number of calls your organization allows in 24 hours.

Some objects could not be saved:authentication provider(for the metadata service).

• Reason:Whataut. manage suppliersThe definition is set to "Increase session to high security"(in Settings->identity verification)
• Solution:
  1. In Salesforce, go to: Settings > Apps > Connected Apps > Use OAuth for Connected Apps page.
  2. click"install" for OwnBackup forSalesforce Metadata Application\Salesforce Sandbox Metadataapp.
  3. After installation, clickManage app policiesand edit the app.
  4. navigate toHigh security session requiredand checkRaise the session level to high securityand click Save.
  5. Go to: Settings > Session Settings > Session Security Levels and checkMulti-factor authentication&User passwordmoved to theHigh securitylist.
  6. Go back to your OwnBacup account andre-authenticatethe service.

API_DISABLED_FOR_ORG

• Reason 1:The Salesforce org does not support API access. API access is available to Enterprise, Unlimited, Performance, and Developer Edition organizations. In this scenario, the data service is backed up successfully, but the metadata service fails with this error message.
• Solution:Contact Salesforce Help Desk if you think your organization should have access to the API and you get an API_DISABLED_FOR_ORG error
• Reason 2:The authenticated user has not activated the API function.
• Solution:
  • Make sure the authenticated user's profile in Salesforce has API permissions enabled.
  • Link to the article on Salesforce user permissions.

SOLICITUD_LIMIT_EXCEEDED

• Reason:This Salesforce error is typically returned when the API quota has been exceeded.
• Solution:
  • Check API consumption in Salesforce: Setup > System Overview > API Requirements. See the maximum number of calls your organization allows in 24 hours for REST and bulk.
  • Contact Salesforce Help Desk if you think your org should have enough API counts in the time period after you receive this message. more on that pleaseread here.

QUERY_TIMEOUT "Salesforce Error: QUERY_TIMEOUT Your query request has been running too long"

• Reason 1:The object is too large to query via the REST API and you must use the bulk API.
• Solution:Configure Bulk API Limitsfrom the Service Options screen.
• Reason 2:When Unlisted Chatter Groups is enabled and permission is not granted. Feed items and feed attachments are specific objects that are vulnerable to this bug.
• Solution:Activate themanage unregistered groups, Permission for the authenticated user's profile.

Mass PK error: internal script error

• Reason:one optimizedThe object queried from the bulk API via the primary key chunk method is in error and was not protected.
• Solution:Contact OwnBackup support for further investigation.

Service backup failed: API is disabled for users

• Reason:The profile permission of the authenticated user's profile cannot connect to the Salesforce API.
• Solution:
  • Make sure the authenticated user's profile in Salesforce has API permissions enabled.
  • Link to the article on Salesforce user permissions.

Service backup failed:INSUFFICIENT_ACCESS: ModifyAllData or ModifyMetadata permissions are required

• Reason:No "Change All Data" permission.
• Solution:
  • Make sure the authenticated user has the ModifyAllData permission. Also verify that the authenticated user has proper access to the specified object and all referenced objects.
  • Link to the article on Salesforce user permissions.

Service backup failed - Cconnected applications connected_applications fail Bulk batch ended with status Error and message: InvalidBatch: Error processing query: INSUFFICIENT_ACCESS: Insufficient access rights to locator ID.

• Reason:No permission to customize the app for the authenticated user.
• Solution:
  • Make sure the authenticated user has the Customize Application permission on the profile.
  • Link to the article on Salesforce user permissions.

Cannot get metadata object

• Reason:Sometimes the Salesforce Metadata API fails to query certain metadata objects.
• Solution:These warnings are temporary and do not require any action and should resolve on their own.

Insufficient access to the specified data category

• Reason:In Lightning for Salesforce, data categories are used in communities. A specific category is marked as invalid.
• Solution:
  • Log in to Salesforce > Settings
  • Go to quick search and look for "data categories". Check the category groups and check which categories are marked as active/inactive.
  • Make sure that the data categories that should be active are marked as active so that communities can be retrieved via the API and accessed by the authenticated user of the service.

sObject not sorted by ID:

• Reason:OwnBackup uses the REST API to request data from Salesforce, which is sorted by record ID when using the Compare, Restore, and Replicate tools. Certain objects cannot be sorted due to Salesforce limitations, so they are excluded from these tools.
• Solution:
  • The respective sObject cannot be sorted.
  • The object is still backed up and available in the backups.

Mass Messaging Sessions Failed: Salesforce Error

• Reason:That's aKnown Salesforce issue that can be encounteredhere.
• Solution:Under Administrative Permissions, enable Access to chat entries for the authenticated user.

• Reason:API limit reached. OwnBackup downloads a number of files (up to the API limit). OwnBackup downloads only new and changed files.
• Solution:The remaining files will be downloaded the next day once the daily API limit is reset.

Content Docs: Salesforce Error: Invalid Character Encoding.

• Reason:ANo UTF-8Characters were used in a content document that is incompatible with the Salesforce API.
• Solution:Solution: Contact OwnBackup support for a list of corrupted IDs. Check and remove the corrupted files to fix this error. For more information, see Salesforcehere.

Timeout Error too many errors in request #1-Warning for "Knowledge item versions" and "Knowledge KAV"

• Reason:Due to lack of permissions for the authenticated user.
• Solution:Grant the authenticated user the following permissions:
  • See draft articles
  • View Archived Articles
• If the error persists, contact OwnBackup support

Too Many Requests – The user sent too many requests in a given period of time.

• Reason:A query was unable to archive multiple records and therefore stopped archiving activity.
• Solutions:Disable the validation trigger or rule that prevents the policy from deleting these records.
• If the problem is caused by a dependency, first archive the referenced dependency before archiving this log.

Cannot write to memory. Check your key management service.

• Reason:The AWS KMS configuration does not allow write permissions to the provided key or alias.
• Solution:Contact your AWS expert to verify the KMSand user configuration.

INVALID_CROSS_REFERENCE_KEY

• Reason 1:INVALID_CROSS_REFERENCE_KEY: Record Type ID - This ID value is invalid for the user. The authenticated user does not have the correct permission for the record type.
• Solution:Make sure that the authenticated user has the correct permission for the record type specified in the error.
• Reason 2:INVALID_CROSS_REFERENCE_KEY: Invalid Cross Reference ID: Parent record is not included in the replication job or permissions issues for the parent object or a lookup relationship is not included in the replication job.
• Solution:Make sure the parent object is included in the replication job. Verify that the authenticated user has access to the primary record referenced in the error. If the relationship is a lookup, make sure the parent object is included in the replication job.

ENTITY_IS_DELETED

• Reason 1:This error occurs in Salesforce when at least one record references a deleted record in the target org.
• Solution:Make sure the record doesn't reference a deleted record (which could also be the record's parent record) in the destination organization.solution 2: If you have manually deleted sandbox data since the last initialization,OwnBackup may not be aware of these changes. In order for OwnBackup to know which records exist in the selected sandbox, you must run a reindex process by clicking Seed in the Template Builder and following the steps in the Seed popup. You can choose whether to index template objects (recommended) or all target objects. Indexing all targets increases initialization duration.

CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY

• Reason:Occurs when an object has a trigger and the data being updated or created causes the trigger to execute and fail. More specifically, it's called an unhandled exception.
• Solution:

  • Modify Apex code to handle exceptions

  • Disable the trigger (you may need to contact the vendor if the trigger is part of a managed package

  • Exclude records that cause the trigger to run

INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST:Status: Invalid value for restricted picklist field

• Reason 1:In the destination org, the value selected in the source environment is not activated. This can be a common mistake as environments evolve over time and change the possible picklist values ​​to choose from during record creation.
• Solution:If objects in the source environment have multiple record types enabled, the value for the record type in the destination environment must also be enabled.
• If the object does not have a record type enabled, the object's picklist value must be enabled in the target environment.
• Reason 2:The source organizational record contains a picklist value that is no longer active. This will prevent you from successfully restoring and inoculating the data. Clean the data and update the value to a current active value.
• Solution:Go to Settings, <Object>, Fields and Relationships, select the PL field and note the inactive values.

'INACTIVE_OWNER_OR_USERNAME'

• Reason:The registry owner in the source environment is disabled in the target environment.
• Solution 1:Enable the Set audit fields and update records with inactive owners permission.After enabling this setting, create a permission set or edit the authenticated user's profile and grant the "Update records with inactive owners" permission.You can enable this permission as followsSalesforce knowledge article.
  Solution 2:Activate the record owner in the target environment.

DUPLICATES_DETECTED" or "DUPLICATE_VALUE: duplicate value found

• Reason:Salesforce found a matching value in a unique identifier field when inserting/updating a record.
• Solution 1:Eliminate duplicate records on the destination.
  Solution 2:Disable duplicate rules in your Salesforce org; seeThis article.Solution 3:If it's a partial sandbox containing records we pushed through the Salesforce update, you'll need to run a reindex process by clicking Seed in the Template Builder and following the steps in the Seed popup. This way, OwnBackup knows which data sets are present in the selected sandbox. You can choose to index the template objects (recommended) or all target objects. Indexing all targets increases initialization duration.

FIELD_CUSTOM_VALIDATION_EXCEPTION:

• Reason:Unless all automations are disabled before the replication/seed job starts, records being seeded will not meet the requirements of the active automations to allow seeding.
• Solution 1:Temporarily disable automations before the job starts. Once the job is complete, re-enable your automations.

  Solution 2:Modify the template or dataset of the datasets included in the replication/seed job to meet the needs of the active automations.
  Solution 3:Update source records to meet the needs of your automations.

ACTIVATION_FAILED

• Reason:Failed to activate/reactivate automations for the job object.
  1. Find permissions to manage and modify flows.
  2. Apex triggers cannot be modified.
• Solution:Confirm that the following permissions are assigned to the integration user
  1. Author Apex.
  2. customize the app.
  3. manage the flow.

FIELD_INTEGRITY_EXCEPTION

• Reason:Try inserting the wrong object ID into the lookup field of the target record.
• Solution:Validate the object ID that is inserted into the lookup field of the target organization record.

SKIP_INSERT

• Reason:Cannot insert a record because of an unsatisfied but required dependency. For example, a search for a parent that does not exist.
• Solution:Check the data ingestion of the main dataset.

STRING_TOO_LONG

• Reason:The field exceeds the field size limit. Watchhelp article.
• Solution:Check the data in the source organization and/or update the field size limit.

INVALID_FIELD_FOR_INSERT_TO UPDATE

• Reason:An attempt is made to anonymize a personal account while the anonymization template contains a replacement value for the Name field that cannot be edited.
• Solution:To anonymize person accounts, set alternate values ​​for FirstName and LastName while omitting the Name field.

INVALID_FIELD: Error deserializing on column {number}

• Reason:A file is missing from the backup, so OwnBackup couldn't restore it during the job.
• Solution:Check if all files/attachments are backed up in the source backup.

An error occurred while retrieving statistics from the organization store. Contact support and provide the following error code: 10076#10035#10200

• Reason:Authentication token revoked or IP access to file backend servers blocked.
• Solution 1:Check if Archive is correctly installed viaThis article.
• Solution 2:Check IP restrictions and make sureAccess to file serversIt's on the white list.

An error occurred during the "Validate Query" operation

• Reason:The new org or updated sandbox is not fully configured.
• Solution 2:Check if Archive is correctly installed viaThis article.

Query timeout: [{"message": "Your query request took too long", "errorCode": "QUERY_TIMEOUT"}]

• Reason:The created policy has reached Salesforce query restrictions and cannot be executed for one or more reasons, e.g. B. because the limit is too high, the range is too large, or the request queries too many tables. This happens when the query exceeds the 120 second query time limit in Salesforce.
• Solution:Lower the limit or reduce the number of items queried. Test a problematic query in the Workbench to ensure it runs within 120 seconds.

Too_many_failures: error limit exceeded

• Reason:A query was unable to archive any records due to a trigger, dependency, or validation rule.
• Solution:Disable the validation trigger or rule that prevents the policy from deleting this record.

  If the problem is caused by a dependency, first archive the referenced dependency before you can archive this log.

Error, the record is considered hot data because it was modified in the last 90 days

• Reason:Hot data is any data that has changed in the last 90 days. This is a protection mechanism that can be manually reset from its default "on" state.
• Solution:Disable hot data protection from the file settings on the application home page and run the policy again.

UNSUPPORTED_APEX_TRIGGER_OPERATION', 'message': 'Apex Event Trigger cannot handle batch operations on recurring events.'

• Reason:Recurring tasks are not supported.
• Solution:When archiving a task object, configure the query to avoid this, e.g. e.g.: "Select the task ID, where LastModifiedDate < LAST_N_DAYS: YIsRecurrence= incorrectLimit 1000"

INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY:Insufficient access rights for cross reference ID: [other record ID]

• Reason:The unarchive requires a reference to the previous record and cannot be accessed by the authenticated user.
• Solution:Check if the referenced record exists. If the record exists, check the authenticated user's permissions for the record. Make sure the authenticated user has the ModifyAllData permission. If the error persists, please contact OwnBackup support.

You cannot specify a version for the sf_com_apps namespace because that namespace is not installed in your organization

• Reason:Make sure the Salesforce Connected Apps package is installed before you install the OB file package.
• Solution:
  • Before installing the OwnBackup Archive app, 'Salesforce Connected Apps' version 1.7 must already be installed in your environment. To verify that you installed the latest version of the app, go to Settings > Installed Packages and look for "Salesforce Connected Apps."
  • If the package does not appear in your installed packages, simply install the app by adding the following string after the Salesforce URL for your instance: https://mysalesforceurl.com/packagingSetupUI/ipLanding.app?apvId=04t30000001DUxx

Error inserting/updating policy Upsert failed. First exception on line 0; First error: STORAGE_LIMIT_EXCEEDED, storage limit exceeded: []

• Reason:Your Salesforce environment has exceeded its limits and new records cannot be created.
• Solution:Manually delete some records to allow Archive to create the archive policy record.

Connection reestablishment by the ConnectionAborted peer

• Reason:The issue may be caused by temporary connection issues with Salesforce. The file tries to run it again but gets the same error. Archive runs the policy on schedule (daily/weekly/monthly).
• Solution:

1. Repeat the process.
2. Wait for the next policy to run.
3. Reduce the number of searches in the policy (if possible from a business point of view).
4. Split the policy if it contains lookups. Add other policies whose root objects are the search child objects.
5. If all of the above measures do not resolve the error, please contact support. There may be an internal optimization that reduces the likelihood of Salesforce throwing this error.

Integration user has limited permissions

• Reason:permission, concessionMissing access to query storage details using the tools API.
• Solution:Add one of the following permissions:
  • API enabled
  • See installation and configuration, and multi-factor authentication
  • Manage multi-factor authentication in the API

FIELD_CUSTOM_VALIDATION_EXCEPTION: You do not have permission to delete this email, sobject_id: None

• Reason:

  When unarchiving, Salesforce may find data validations such as B.: validation rules, restricted pick list, duplicate rules, etc. In addition to this error message, you may see additional text with:validation Rule Message,sf_delete_error_message_object: Status code.

• Solution:Disable validation rules.

FIELD_CUSTOM_VALIDATION_EXCEPTION: invalid value for restricted picklist field

• Reason:

  When unarchiving, Salesforce may find data validations such as B.: validation rules, restricted pick list, duplicate rules, etc. In addition to this error message, you may see additional text with:validation Rule Message,sf_delete_error_message_object: status_code: FIELD_CUSTOM_VALIDATION_EXCEPTION, error_message: invalid value for narrowselectlist field: closed lost - account merged; Source class: UpdateOpportunityBeforeMergeAccount, sobject_id: 001C000001CVN1sIAH

• Solution 1:

1. Disable the restricted picklist value.
2. Add a new value.

• Solution 2:

1. Check the restricted selection list option.
2. Uncheck the new picklist value and replace it with the existing picklist value.

stopped process

• Reason:

  The operation failed as part of the bulk delete operation.

• Solution:Update configuration settings:

1. Disable the permanent delete option in the file settings
2. Disable the lookup relationship (if possible). When one of the children cannot be deleted due to the lookup relationship.

INVALID OPERATION

• Reason:

  What "Enable draft emails for cases"The function is not activated.

• Solution:To embed the email, add the option to enable email drafts:read more here

unknown exception

• Reason:

  The operation failed for an unknown reason.

  (Video) Best Practices For Salesforce Data Lifecycle Management

• Solution:

1. Remove the purge and try running the policy again.
2. Remove the search for the policy and try running the policy again.
3. Try to delete the bad records manually.
4. If none of the above works, please submit a case to Salesforce Support.

DELETE_OPERATION_TOO_LARGE: Cascading dereferencing of too many records

• Reason:

  This issue is usually the result of a large number of records associated with the deleted record through a master-detail or lookup relationship..

• Solution:

To troubleshoot performance issues when deleting records, identify and delete the related records and empty them from the Recycle Bin.keep reading