# Deprecation Policy

## Potential customer impact

* Large: could prevent use of service if the customer relies on the feature.
* None: totally transparent, depending on customer usage of the service.

## Examples

* Complete removal of a feature from the UI.
* Shutting down `api/v1/foo`.

## Frequency

Rare (\~1 or fewer per year)

## Communication before the change

* Guaranteed: multiple email notifications to all registered WarpStream users, starting at least 180 days before the deprecation date, with details about the change and available alternatives.
* May also include: in-app messaging; updated documentation and release notes; communication from Sales and customer support.

## Timing of the change for each customer

100% at Confluent’s discretion.\\


---

# Agent Instructions: 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:

```
GET https://docs.warpstream.com/warpstream/reference/deprecation-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.