> 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/investing/macro-and-liquidity/sector-etf-flows/faqs.md).

# FAQs

Sector ETF Flows FAQs

<details>

<summary>Why does the indicator require a 1D timeframe or higher?</summary>

Sector ETFs report their total assets under management (AUM) and share counts at the end of the trading day. Therefore, accurate flow data is only available on a daily or higher timeframe.

</details>

<details>

<summary>What does a high Z-Score mean for a sector?</summary>

A Z-Score measures how many standard deviations a recent flow is from the historical average. A Z-Score above +2.0 indicates a statistically extreme inflow event (heavy accumulation), while a score below -2.0 indicates extreme distribution. These extremes can highlight periods of capitulation or euphoric buying.

</details>

<details>

<summary>Which sectors indicate a "Risk-On" environment?</summary>

Typically, strong inflows into Technology (XLK), Consumer Discretionary (XLY), and Communication Services (XLC) signal a "risk-on" appetite, indicating that investors are confident and seeking growth.

</details>

<details>

<summary>Which sectors indicate a "Risk-Off" environment?</summary>

When capital aggressively rotates into defensive sectors like Utilities (XLU), Consumer Staples (XLP), and Healthcare (XLV), it signals a "risk-off" environment, indicating investors are seeking safety and dividend yield over growth.

</details>

<details>

<summary>Can I hide specific sectors from the dashboard?</summary>

Yes. In the indicator settings, you can individually toggle each tracked sector ETF on or off, allowing you to create custom aggregate views or focus purely on a specific subset of the market.

</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/investing/macro-and-liquidity/sector-etf-flows/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.