> For the complete documentation index, see [llms.txt](https://doc.moost.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.moost.io/platform-manual/rules/rule-configurator/streak.md).

# Streak

A rule can be used for Streaks. Therefore you can turn on the "Streak" feature, and define a streak condition.

<figure><img src="https://2791588365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkz3AVy8mukfhOsBy0Lvo%2Fuploads%2Fgh3IGQgUmO8Gs8XFKAoR%2Fimage.png?alt=media&amp;token=1e6febe3-557a-479c-ab9d-451304eba60a" alt=""><figcaption><p>Streak Rule</p></figcaption></figure>

The streak condition can be expressed as a mathematical expression producing a boolean value. It works exactly the same as the "Condition" field.&#x20;

Have a look at [Rule Language](/platform-manual/rules/rule-language.md) to see the full feature set of the expression language.

A notification is sent if both the "Condition" *and* the "Streak Condition" expression is fulfilled. If the "Streak Condition is fulfilled, the streak counter is incremented, otherwise the streak counter is reseted.

The variable StreakCounter can also be included in the message text or the title of a notification. It represents how many times the streak was already matched.

<figure><img src="https://2791588365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkz3AVy8mukfhOsBy0Lvo%2Fuploads%2FwuZPEAhcvIXB5kCdMQnG%2Fimage.png?alt=media&amp;token=9426a87e-419a-4fbd-8817-87502d4cae8f" alt=""><figcaption></figcaption></figure>


---

# 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://doc.moost.io/platform-manual/rules/rule-configurator/streak.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.
