> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/operate/maintain-and-change/dialogue-manager-retention.md).

# Dialogue Manager retention

Plan Dialogue Manager retention for old processed text-dialogue data.

Dialogue Manager includes a database retention procedure for removing old processed text-dialogue data. In cloud deployments, run retention only through the supported operations or support process.

{% hint style="danger" %}
Retention removes data. Agree the retention date, execution owner, validation method, and rollback expectations with support or operations before any retention action is run.
{% endhint %}

## What retention does

Retention removes:

* conversations with no recent processed messages before the retention date
* orphan messages older than the retention date
* orphan attachments
* old reference records

Open conversations or conversations with recent processed messages are not in scope for removal by the current procedure.

## Before requesting retention

Confirm these details before support or operations runs retention:

| Detail                 | Why it matters                                                              |
| ---------------------- | --------------------------------------------------------------------------- |
| Retention date         | Defines the earliest data that must remain available.                       |
| Target environment     | Prevents retention from running against the wrong UCC, region, or database. |
| Business approval      | Confirms the data-removal window is accepted.                               |
| Validation sample      | Defines which conversations or reports should be checked after retention.   |
| Recurrence requirement | Determines whether a one-time action or scheduled process is needed.        |

## Request retention

1. Confirm the retention date with the business owner.
2. Confirm the target UCC, region, or Dialogue Manager environment.
3. Confirm whether retention is one-time or recurring.
4. Request execution through the supported operations or support process.
5. Wait for confirmation that retention completed.
6. Validate the agreed sample data or reports.

{% hint style="warning" %}
Do not run the retention stored procedure directly from SQL tooling unless support or operations explicitly confirms that you own execution for the environment.
{% endhint %}

## Recurring retention

If recurring retention is required, agree the retention period and execution schedule with support or operations. Do not create an unsourced database automation schedule from legacy examples.

## Validation

After retention completes:

1. Confirm that current and recently processed text conversations are still available.
2. Confirm that old processed data is no longer returned in the agreed validation sample.
3. Record the retention date, execution window, and support or operations reference for audit purposes.


---

# 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://atlas.anywhere.now/operate/maintain-and-change/dialogue-manager-retention.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.