> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/oscillators/oscillator-concepts-tm/divergences.md).

# Divergences

<figure><img src="https://3870127617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBVnUk5c5TVytimjy972%2Fuploads%2Fgit-blob-cab9367ba0c928999ba58877423ba29887b5f127%2Fdocs-oscillator-concepts-011.png?alt=media" alt=""><figcaption></figcaption></figure>

A divergence is a polite refusal. Price prints a new extreme, but The Line doesn’t back it up. That can hint at exhaustion, absorption, or stealth accumulation/distribution.

### **Quality over quantity**

A stricter mode focuses on divergences built at meaningful distance from the band and filters casual mid‑range wiggles. The goal is fewer but clearer opportunities.

### **How to act**

* **Build a case:** divergence + fading participation + softening stripe.
* **Time it:** use a **re‑entry** toward the band, a failure test at structure, or a simple “stop‑going” bar for trigger.
* **Risk:** place invalidation beyond the extreme that formed the divergence and scale out into nearby structure.

### **Expectations**

Not every divergence leads to a full reversal. Many simply resolve into a pause or a two‑leg pullback. Trade the *first turn*, then reassess.

### **Visibility**

Marks and traces are compact—easy to review, unobtrusive live. If you want a clean pane, show only confirmed marks.


---

# 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://docs.candelacharts.com/oscillators/oscillator-concepts-tm/divergences.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.
