> 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.6-monthly-release-notes.md).
# Backup & Archive (v4.5.6) - Monthly Release Notes
{% hint style="info" %}
## Release Details - Backup & Archive - v4.5.6 - January 28th, 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 %}
##  Summary
This article documents the patch release for **Backup & Archive (v4.5.6)**. This release adds support for self-hosting the Backup & Archive app, the **Add all dependents** toggle, and several bug fixes.
###  License Manager Support for Self-Hosted Backup & Archive
Support for License Manager is now available for the self-hosted Backup & Archive app.
* The **Global Settings** app now shows an **ENTER LICENSE KEY** button for customer-hosted Backup & Archive deployments.
* Entering a valid license key provided by the Flosum team grants access to the cloud app.
###  Add All Dependent Toggle for Archive Templates
Included an “**Add all dependents**" toggle in the **Child Objects** popup for archive templates.
* This toggle allows you to quickly add all child objects that are automatically deleted when the parent record is deleted.
* When enabled, all child objects marked as Dependent are automatically selected, eliminating the need to add each dependent object individually.
###  Bug Fixes
* Fixed an issue in **Archive Jobs** where the job failed with the error:\
“*Data too long for column 'recursive\_chain' at row 1.*”
* Resolved an issue on pages with tables and a **Full Screen** button where entering text containing the letter “**F**” incorrectly triggered full-screen mode.
* Corrected label typos:
* **Archive Template → Add Child Objects pop-up**: Replaced “**Depended**” with “**Dependent**”
* **Restore Archive → Select Object step → Add Child Object pop-up**: Replaced “**Depended**” with “**Dependent**”
* Fixed an incorrect toast message displayed when deleting a template. This was caused by an unnecessary backend request for scheduler details, which has been removed.
* Fixed an issue where switching organizations from the **Search** page retained object selections from the previous org, requiring a page reload.
* Resolved an error encountered during restore jobs:\
“*FieldDefinition does not support queryMore() in restore request.*”
---
# 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.6-monthly-release-notes.md?ask=&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.