> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/settings/analytics/anomaly-detection.md).
# Anomaly Detection
Under **Settings → Modules → Analytics → Anomaly Detection**, this page flags data points that fall outside expected patterns, an unusual spike in returns, a sudden drop in a region's sales. This page controls where those flags appear and how many are shown before Tellius suppresses them.
{% hint style="info" %}
These are query-time settings. They govern how anomalies are surfaced on charts as users work, not how anomalies are detected or scheduled.
{% endhint %}
#### Display anomalies in Search
When on, anomalies are displayed for all charts in the Search module by default.
#### Display anomalies in Explore (Vizpads)
When on, anomalies are displayed for all charts in Explore (Vizpads) by default.
{% hint style="info" %}
These two toggles are independent. Individual charts may still be able to override this setting.
{% endhint %}
#### Set the anomaly limit per chart beyond which the anomalies will be hidden
Anomalies are hidden on any chart that exceeds the number specified here.
This exists because anomaly markers stop being useful past a certain density. A chart with 200 flagged points communicates nothing; the flags become noise and obscure the data underneath. Set this low if you want only the cleanest signals surfaced.
#### Saving
Click **Save** to apply your changes, or **Cancel** to discard them. Save stays inactive until something changes.
---
# 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://help.tellius.com/settings/analytics/anomaly-detection.md?ask=&goal=
```
`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.
