> 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.4.0-monthly-release-notes.md).
# Backup & Archive (v4.4.0) Monthly Release Notes
{% hint style="info" %}
#### Release Details - Backup & Archive - \[v4.4.0 - August, 2025]
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)
* Works with User Pool App v1.5.4
{% endhint %}
##  Summary
The **Backup & Archive v4.4.0** release introduces several new features, including the ability to import backups, access backup and archive data even after a Salesforce Connection has expired, and a Record Count column on the Backup & Archive History page. Additionally, numerous enhancements and bug fixes have been applied to existing features.
##  New Features
###  Import Your Backups
We’re excited to introduce the Import Backups feature in the Backup & Archive (B\&A) app, which enables you to import previously exported data from an AWS S3 bucket. This one-time import helps you retain and access historical backups directly within the B\&A app. After entering your S3 bucket credentials, you can select which backup entries to import. Once the import job completes successfully, a Composite & Sync process runs automatically to integrate the data.
{% stepper %}
{% step %}
### Enter S3 Credentials
Provide your AWS S3 bucket credentials so the app can access exported backup files.
{% endstep %}
{% step %}
### Select Backup Entries
Select which backup entries from the S3 bucket you want to import into the B\&A app.
{% endstep %}
{% step %}
### Composite & Sync
After the import job completes, a Composite & Sync process runs automatically to integrate the imported data into the app.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
Important Considerations:
* One-time Import per Org: Multiple files can be included in one job, but additional imports are blocked once Composite & Sync starts.
* Data Retention Limit: By default, only the last 12 months (based on *Last Modified Date*) are imported. Contact your Flosum Success Manager to include older data.
* Supported Content: Data and binary files are imported; **metadata is not imported**.
* UI Limitation: The *Import Backup* button will be disabled if there is already backup data in B\&A. Contact your Success Manager to import from an external source.
{% endhint %}
***
###  Access Backups & Archives Post Org Expiration
Starting with the August 2025 release, you can continue to access your Salesforce org's backups and archives even after the org has expired, without needing to update or refresh the Salesforce access token.
What you can do:
* View backups and archives
* Export data
* Search historical data
* Purge data in line with compliance policies
What’s restricted:
* Backup, archive, and restore operations are not available for expired orgs.
This ensures you retain access to historical data and remain compliant with retention or audit requirements, even if the source Salesforce org is no longer active.
***
###  Record Count in Export Job History
The **History** table for export jobs now includes a new **Records** column that shows the **total number of records** exported for each job. For detailed insights, including **record count per object**, view the **Logs** tab within the individual export job.
***
##  Improvements
Rich Text Field Image Handling
Previously, backup jobs could fail if an image embedded in a rich text field lacked an "alt" text parameter. This issue has been addressed: backup jobs will now continue even if such images lack "alt" text. The record will still be backed up; only the image without the "alt" text will be skipped.
The job logs will show a warning like this:
{% code overflow="wrap" lineNumbers="true" %}
```
[warning] Agent__c (Id: a3hDD0000025twNYAQ): invalid or missing alt text in field RichTextArea__c. Image in rich text field RichTextArea__c was not backed up.
```
{% endcode %}
Now:
* Backups continue without interruption.
* The affected image is skipped, with a clear warning in the logs.
Support for Salesforce API Version 64.0
The Backup & Archive application now supports Salesforce Platform API Version 64.0 to ensure continued compatibility with Salesforce updates and features.
UI Enhancements
These additions improve date entry efficiency and give users better control over calendar interactions.
* Child Object Selection Highlight: In Templates, Restore Requests, and Search Jobs, the child object selection chip is now visually highlighted for quicker recognition.
* Restore Requests Config Highlight: Fields and Automation Processes sections now highlight at the object level when configurations are applied.
* Calendar Enhancements: The calendar control now includes Today and Clear options:
* Today — instantly select the current date
* Clear — remove the date
***
##  Bug Fixes
1. Purge Job Error on Deleted Records: Resolved "The path argument must be of type string. Received undefined" when purging records that had already been deleted from the Salesforce org. Purge jobs now remove such records from the app without error.
2. Count Records on Profile Object: Fixed errors caused by field labels exceeding 60 characters when using the Count Records feature or applying filters on the Profile object. You can now filter Profile and get accurate record counts without errors like: "fieldsDescribe.XXX.label must be shorter than or equal to 60 characters."
3. Record Count Mismatch in Archive Job Summary: The Data tab now correctly reflects the total number of archived records. Logs now show both backup and archive totals. (The archive process first backs up records according to the archival template—if not already present—then archives them from Salesforce. The UI and logs now clearly reflect both steps.)
4. Formula Field Type Display in Search Requests: Fixed incorrect field type display when applying filters on formula fields during search request creation; the correct field type now shows.
5. “Exceeded max size limit of 6000000” Error: Optimized object-describe calls to return only required metadata to avoid oversized Apex responses. This fix is included in the Backup & Archive Salesforce package version 1.24. Please upgrade the package from the Integrations tab in the Backup & Archive Application Settings page.
---
# 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.4.0-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.