> 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/toolkits/orderflow-concepts-tm/alerts.md). # Alerts The Order Flow Concepts toolkit includes specialized alerts designed to keep you informed of critical liquidity events and traps, even when you aren't actively monitoring the chart. ### Alert Settings * **Enable Alerts**: The master switch to enable or disable all alerts from this indicator. If this is disabled, no alerts will fire. ### Alert Types You can independently toggle the following alert conditions: * **Trapped Traders**: Fires when the model detects that retail traders have been baited into a breakout and immediately trapped by a reversal. * This alert is split internally, notifying you specifically if it is "Trapped Bulls" or "Trapped Bears". It is an excellent trigger to look for fading opportunities. * **Strong Liquidity Reached**: Fires when current price successfully reaches and taps a major active liquidity pool (as defined by your Liquidity Mappings settings). * This is your signal to pay attention to the chart and monitor for the reaction: will price absorb the liquidity and reverse, or push through and continue hunting? --- # 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/toolkits/orderflow-concepts-tm/alerts.md?ask=&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.