Salesforce Docs Portal

Archive Limitations

Various limitations and unsupported features for archiving, unarchiving, and other functionalities within the Archive managed package, including policy record limits, object exclusions, and operational constraints.

Note
Note This content relates to Archive. For Salesforce Archive, see Store Data Externally with Salesforce Archive.

Archive Policy Record Limits

A single archiving policy is restricted to 2 million root records.

Users who archive more than 2 million records are recommended to set multiple archive policies at complimentary time intervals with the same SOQL.

When setting multiple policies with the same SOQL, or policies with the same date range, make sure to schedule them to run at different times to avoid collisions.

These objects aren't supported in Archive:

Unarchiving

Unarchiving is only available for root objects. When you unarchive a root object, Archive also restores all lookup records that were archived with it.

The following items are not supported for unarchiving:

  • An Account with an Inactive Account Team Member.
  • A Case with an Inactive Case Team Member.
  • Content Documents in Private Libraries.
  • FeedItems
  • ActivityFieldHistory objects (not supported for unarchiving or exporting).
  • Oversized EmailMessage HTML Body fields
  • Embedded Images in Unarchived Emails: Inline images do not display in the restored record because the unarchive process creates a new record ID, breaking the original HTML links.

Knowledge Articles

Archive actions are only supported when these criteria are met:

Recurring Activities

  • When archiving a task or an event as a root, the task or the event is part of the series. Simply, when archiving recurring tasks or events, the archive includes all future tasks and events in the series, even if they aren't part of the original SOQL.
  • When archiving a root where the child records are part of a recurring series, only the child is deleted, not the entire series.
  • To delete the series, the policy must be defined on the task or event.
  • Unarchive of recurring tasks and events are archived without the series flag and their relation to the parent record (task or event).

    These fields appear empty as they refer to a series that has been broken.

    Events
    • IsRecurrence
    • IsRecurrence2
    • IsRecurrence2Exception
    • Recurrence2PatternStartDate
    • Recurrence2PatternText
    • Recurrence2PatternVersion
    • RecurrenceActivityId
    • RecurrenceDayOfMonth
    • RecurrenceDayOfWeekMask
    • RecurrenceEndDateOnly
    • RecurrenceInstance
    • RecurrenceInstance
    • RecurrenceMonthOfYear
    • RecurrenceTimeZoneSidKey
    • RecurrenceType
    Tasks
    • IsRecurrence
    • RecurrenceActivityId
    • RecurrenceDayOfMonth
    • RecurrenceDayOfWeek
    • RecurrenceInstance
    • RecurrenceInterval
    • RecurrenceMonthOfYear
    • RecurrenceRegeneratedType
    • RecurrenceStartDateOnly
    • RecurrenceTimeZoneSidKey
    • RecurrenceType

Deleted Objects

Deleted Objects aren't supported for Archive Search or Archive Widget. To be referenced in Archive Search or Archive Widget, Objects must be live.

Objects Excluded from Archive Search

Some objects are excluded from Archive Search by default and don't appear as searchable options, even when the object is included in an archive policy and its records are archived.

  • Objects with the standard suffixes Feed, History, Relation, Role, and Share
  • LiveChatTranscriptEvent

Mobile Widget

The Mobile Widget only shows the first three columns defined in your widget. The mobile widget doesn't support CustomListRelatedRecordArchivedWidget or CustomSingleRelatedRecordArchivedWidgets.

The Field Service app is not supported for the Archive Mobile widget..

Archive Search Widget Constraints

The Archive Search Widget is subject to specific Salesforce Platform security and data volume constraints.

  • Including the Activity ID field in the widget search layout for EmailMessage records can cause system errors in orgs with high data volumes. Typically, these errors occur in orgs with more than 100,000 distinct activity references.
  • To view the Activity ID field in the widget, assign users the View All Data user permission. This permission allows the system to bypass sharing rule evaluations for polymorphic fields, such as WhoId or WhatId.
  • If your users don’t have the View All Data permission, remove the Activity ID field from the EmailMessage widget search layout. This makes sure that all other fields in the widget display correctly.
  • The Archive Search widget monitors Apex heap memory during result formatting and stops at approximately 9.5 MB (95% of available heap). This limit affects the total rows, fields, and processing overhead, not individual field size or response volume. Large fields like EmailMessage.HtmlBody use more memory. To maximize results, reduce the number of fields selected or exclude large-content fields.

CustomListRelatedRecordArchivedWidget

When object sharing is enabled using this widget, the summary total of records displayed isn't accurate.

CustomSingleRelatedRecordArchivedWidget and CustomListRelatedRecordArchivedWidget

These widgets aren't currently supported in Experience Cloud.

File Download Limitations

  • The file size is limited by what can be transferred within 15 minutes, typically up to 5GB on standard internet connections.
  • For files larger than 5GB, we recommend exporting to an AWS S3 bucket. Only relevant for archived file.
  • If a download stops due to a timeout, click Resume to continue the download. The download remains resumable for up to 15 minutes after the timeout, after which you must restart the download.
  • The download process is limited to 15 minutes.