> For the complete documentation index, see [llms.txt](https://docs.tivity.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tivity.one/administration/breaking-changes.md).

# Breaking changes

## Version 19

### Issue 1222

#### Change&#x20;

Temporary files are now saved under different folders based on purpose.

Files for immediately processing are stored under `<Core-Temp>/Processing`, files to be persistent later are stored under `<Core-Temp>/Registry`, and files cached by source adapters are stored under `<Core-Temp>/Sources`.

#### Migration

The platform administrator may delete all folder and files under \`\<Core-Temp>\` except the folders listed above.

## Version 17

### Issue 1169

#### Change

A typo was fixed in the share message template.

The placeholder `{SEMDER_LAST_NAME}` was changed to `{SENDER_LAST_NAME}`.

#### Migration

The platform administrator has to update the templates.


---

# 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.tivity.one/administration/breaking-changes.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.
