> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/backend/backend-api/older/backend-api-version-15.2.4.md).

# Backend API Version 15.2.4

## Known Issues

This update may have caused existing Azure Function sessions to be logged out. Please follow the instructions in the [link](/sso-connect-cloud/device-approvals/automator.md#installation-method-azure-container-app) to re-activate the Azure Function.\
\
See the "**Troubleshooting and Repairing Failed Logins**" section to resolve the issue.

## Features & Improvements

* KA-3777: Added reporting module event for "User requesting self-device approval" for SSO Cloud
* KA-3772: Ensure BreachWatch is granted to linked personal accounts
* KA-3716: Modified sync to allow single-record retrieval for the Commander SDK
* KA-3798: New "Share Report" API for Vault and Commander SDK

## Bug Fixes

* KA-3727: Attempt to add a Trusted User generates a "No Active Share Exist" error message
* KA-3710: Admin approvals randomly fail to be received in the Vault
* KA-3689: Log Error - error setting master password expiration
* KA-3627: Adding an alias for an SSO user fails
* KA-3027: Issue causing transferred records to have two owners
* KA- 2672: "Removed record permission" event fails to be triggered
* KA-3827: Transferring an account can create a "read only" owned record
* KA-3767: Unable to logout from SSO Cloud if there is no IdP session id
* KA-3842: Commander times out after 30 days
* KA-3027: Transferring a record, the new owner deletes the transfer record, went to the original owner's trash can.
* KA-3827: Transferring an account can create a read-only owned record.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/release-notes/backend/backend-api/older/backend-api-version-15.2.4.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.