> 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.7.23-monthly-release-notes.md). # Backup & Archive (v4.7.23) - Monthly Release Notes {% hint style="info" %} #### Release Details - Backup & Archive - v4.7.23 - September 03, 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 monthly release for **Backup & Archive (v4.7.23)**. This release updates how Salesforce objects are displayed throughout the application so that every selector, tree, and summary shows both the object label and the object API name in a consistent format. It also removes an unnecessary redirect from the template configuration flow, so you stay on the screen you were working on after saving. Both changes streamline the process of configuring templates and jobs against a large Salesforce organization. An update to this release also makes restores more reliable when Salesforce reports record-locking errors, by retrying the affected records sequentially instead of in parallel. ### ![](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) Improved Object Display Across the Application #### What Changed The object display format has been updated across the application. Object selectors, trees, selected-object lists, summaries, and related configuration panels now show both the Object Label and the Object API Name in a consistent format. For example: * `Account — Account` * `Account History — AccountHistory` Object search has also been updated, so you can search by either the Object Label or the Object API Name. #### Why It Was Done Showing the label and the API name together makes Salesforce objects easier to identify when selecting and reviewing them. #### What You Will Notice The new format appears across Templates, Restore Backup, Restore Archive, Point-in-Time Restore, Export, Search, and Organization Notifications, as well as in the lists and panels that display selected objects. Searching by API name now returns the object you expect, which helps when several objects have similar labels. ### ![](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) Improved Template Configuration Flow #### What Changed After you save a validated query or configuration, you now remain on the current configuration screen instead of being returned to the first screen of the template configuration. Existing validation and save functionality are unchanged. #### Why It Was Done Previously, saving could redirect you back to the first screen of the template configuration. Continuing your work meant reopening the relevant configuration screen and waiting for it to load again before you could review the Object Structure. #### What You Will Notice You can keep configuring a template immediately after saving, with no extra navigation and no additional loading time. The Object Structure remains available on screen. ### ![](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) Improved Restore Handling for Salesforce Record Locking #### What Changed Backup & Archive now handles Salesforce record-locking errors more reliably during restore operations. When Salesforce returns an `UNABLE_TO_LOCK_ROW` error while records are being restored in parallel, Backup & Archive automatically retries the affected records using sequential processing. If those records continue to encounter record-locking errors, the restore process reduces the chunk size and retries them again. #### Why It Was Done Salesforce can return an `UNABLE_TO_LOCK_ROW` error when multiple records are restored in parallel and some of those records are locked by another Salesforce operation. This is especially relevant when restoring related records, master-detail relationships, or records with roll-up summary fields. The updated restore logic reduces parallelism only when a record-locking conflict is detected, so the normal parallel restore process continues when no locking issues occur. #### What You Will Notice When a restore operation encounters an `UNABLE_TO_LOCK_ROW` error: * The records affected by the locking error are identified and retried. * The affected records are retried sequentially instead of in parallel. * If the locking error occurs again, the restore chunk is reduced and the records are retried. * Records that were restored successfully do not need to be processed again. This improves restore reliability in Salesforce environments where record locking can prevent parallel restoration. Sequential retries may increase the restore time for the affected records. This is an expected trade-off when handling Salesforce record-locking conflicts. --- # 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.7.23-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.