> 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.6.1-monthly-release-notes.md).
# Backup & Archive (v4.6.1) - Monthly Release Notes
{% hint style="info" %}
## Release Details - Backup & Archive - v4.6.1 - Febuary 26th, 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**
* **Global Settings** app version **1.6.10** or later
* Backup & Archive tenant setup
* Appropriate Flosum user permissions (SystemAdministrator or equivalent)
{% endhint %}
##  Summary
This article documents the patch release for **Backup & Archive (v4.6.1)**. This release adds support for improved job notifications, access control for data in the Backup & Archive Salesforce package, and bug fixes.
{% hint style="info" %}
#### Self-Hosted
**Backup & Archive (v4.6.1)** requires **Global Settings (v1.6.10)** or later.
{% endhint %}
###  Improved Job Exception Notifications
The job completion notifications now feature clearer, more user-friendly messages for known exceptions, such as expired tokens. For unanticipated errors, the notification states: `Unhandled exception occurred (see logs for details).`
Email notifications for completed jobs now clearly state if the job was successful or finished with exceptions.
###  **Backup History Access Control Improvement**
To enhance access control, the Backup History component in the Backup & Archive Salesforce package now only displays data from objects the user has permissions to access. Upgrade to version 1.2.0 to use this feature. For update instructions, see the following article.
* [Changing Integrations Settings](/backup-and-archive/settings/organization-settings/backup-and-archive-settings-integrations.md)
###  Bug Fixes
* **Resolved 403 Unauthorized Error**: Fixed an issue causing intermittent HTTP 403 (Unauthorized) errors. User sessions now remain valid as expected, preventing unauthorized access failures.
* **Resolved ENOSPC Error During Backup Import**: Fixed an issue where importing backups could fail with the error: `ENOSPC: no space left on device.`
---
# 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.6.1-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.