> 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/interbank-price-action-tm/faqs.md).

# FAQs

<details>

<summary>How to change Order Blocks detection?</summary>

Order Block detection is closely tied to the length of the Micro Market Structure. To adjust the detection length of Order Blocks, you need to modify the Market Structure's internal settings and change the length to the desired value.

</details>

<details>

<summary>How to change Swing Order Blocks detection?</summary>

Swing Order Block detection is directly linked to the swing length of the Macro Market Structure. To adjust the detection length for Swing Order Blocks, modify the swing settings of the Market Structure and set the length to the desired value.

</details>

<details>

<summary>How to change Breaker Blocks detection?</summary>

The detection of Breaker Blocks is directly linked to the length of the Micro Market Structure. To adjust the detection length for Breaker Blocks, you need to modify the internal settings of the Market Structure and set the length to your desired value. Same how is done for Order Blocks.

</details>

<details>

<summary>Why not all Breaker Blocks are detected?</summary>

The Breaker Blocks detection is influenced by the Length, Hide Overlap, and Position settings. Be sure to adjust these settings to suit your needs.

</details>

<details>

<summary>How to change Premium &#x26; Discount detection?</summary>

Premium & Discount detection is directly tied to the length of the Market Structure. To adjust the detection length for Premium & Discount, you need to modify the Market Structure's Micro settings and set the length to your desired value, just as you would for Order Blocks.

</details>


---

# 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/interbank-price-action-tm/faqs.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.