> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.5.3-monthly-release-notes.md).

# Backup & Archive (v4.5.3) - Monthly Release Notes

{% hint style="info" %}

## Release Details - Backup & Archive - v4.5.3 - January 13th, 2026

This article is intended for Salesforce administrators, compliance officers, and IT teams responsible for managing Salesforce backups and data governance.

**Release Type**

* Monthly
* Applies to Flosum-hosted and self-hosted

**Prerequisites**

* Backup & Archive tenant setup
* Appropriate Flosum user permissions (SystemAdministrator or equivalent)
  {% endhint %}

## ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FPL2eaOdTi7VscAjFymsv%2FSummary2-Small-Icon.svg?alt=media\&token=a14ffcd6-66df-43ec-aafc-61364d19c7cd) Summary

This article documents the patch release for **Backup & Archive (v4.5.3)**. This release adds a new Declarative Filter operator and improves job scheduling.

### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FgG2A2IRhOXknRFbAGToW%2FNew-Feature-Icon2-Small.svg?alt=media\&token=76ce09b1-243a-482d-97e4-ccc4cbc94d67) Added Support for the `IN` Operator in Declarative Filters

Added support for the `IN` operator in the declarative filter. It can be used to filter records by `recordId`.

{% hint style="info" %}

#### Max recordIds

A maximum of **200** `recordIds` allowed per filter row (limit from Salesforce). You can add up to 5 filter rows, enabling searches of up to **1000** `recordIds`. Use the following **Custom Logic** `(1 OR 2 OR 3 OR 4 OR 5)` to combine the filter rows 1 through 5.
{% endhint %}

The `IN` operator is supported in filters for the following:

* Export
* Search Request
* Restore Request
* Templated Backup > Declarative Filter
* Templated Archive > Declarative Filter

{% hint style="info" %}

#### Field Type Limitations

The `IN` operator adheres to the Salesforce-supported field type limitations and is not supported for the following field types:

* **Geolocation**
* **Address**
* **Encrypted Text**
* **Blob**
* **Rich Text Area**
* **Formula fields**
  {% endhint %}

### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FFX1KImFkBpbzYgGoBLl6%2FEnhance-Icon-Small.svg?alt=media\&token=6211adf4-19a2-458d-92fc-54b77a2a635a) Updates to Export Job Processing

An Export job can now run in parallel with one backup or restore request job, which includes:

* Any type of Backup job: Templated, Scheduled, or Composite.
* Any type of Restore Request job: Backup, Archive, or Metadata. (This does not include executing a restore request.)

All scheduled jobs will continue to run as per their defined schedules.

{% hint style="info" %}

#### Important Export Job Notes

* Users will no longer see errors indicating that a backup or restore cannot start because an export is in progress.
* If a backup or restore is already in progress, a new export will start only after the backup or restore completes.
* Multiple exports cannot run in parallel within the same org.
  {% endhint %}

{% hint style="info" %}

#### New `IN` Declarative Filter Operator Notes

The Declarative Filter for an Export job is limited to select fields like Id and Name. However, adding the `IN` operator broadens your filtering choices. For quicker Export performance, using a Declarative Filter is recommended.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flosum.com/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.5.3-monthly-release-notes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.