> 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.5-monthly-release-notes.md).

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

{% hint style="info" %}

#### Release Details - Backup and Archive - v4.6.5 - Mar 24, 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**

* A registered and configured Flosum Cloud Apps tenant
* 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 and Archive (v4.6.5)**. This release focuses on improving restore reliability by addressing tenant resolution issues during **Create Restore** and strengthening import handling for inconsistent field lengths and types to prevent restore errors.

### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FPkkIrCHYIMWUxWg36UuL%2FBug-Icon-Small.svg?alt=media\&token=b5a25c17-8b87-4ad9-a585-0058eccb3f95) Bug Fixes

* Fixed an issue in **Create Restore** where the error “**Organization not found**” could appear, blocking the restore workflow even when the organization was available.
* Fixed an issue where Account data could be skipped during import because the restore logic expected an 18-character value, but the source data field could have a different length or type. This update improves validation and handling to prevent skipped records and restore failures.


---

# 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.5-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.