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

# Backend API 18.1.4

### Improvements

* Improved reliability of folder hierarchy when moving and deleting nested shared folders, ensuring subfolders remain correctly placed after sync

### Bugs

**KA-8864:** Fixed an issue where deleting a folder's previous parent could incorrectly remove a moved subfolder tree from its new location. Nested shared folders that were moved and then had their original parent deleted now remain properly synced in their new location.

**KA-8877:** Fixed an issue where restoring a folder tree from the trash could produce duplicate folder references during sync. After restoring nested folders from the trash, the system now correctly rebuilds the folder hierarchy without creating extraneous parent associations that could lead to unexpected behavior.

**KA-8894:** Fixed an issue where workflow notifications were not being delivered to some users. Workflow-triggered notifications now reliably reach all intended recipients.


---

# 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://newdocs.keeper.io/en/release-notes/backend/backend-api/backend-api-18.1.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.