> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-3-user-manual/dashboard/alarms_and_warnings/alarm-limits.md).

# Alarm limits

Understand warning vs alarm limits and how they behave.

The alarm limits may be defined as warnings or alarms.

Alarm limits define when a measuring point reading becomes a **warning** or an **alarm**.

An example of a graph with limits is shown below.

See also: [Graph tab](/boomerang-3-user-manual/dashboard/object_view/detailed-object-view/graph-tab.md).

<figure><img src="https://3588014471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEANwXRnuP0ug8971viyg%2Fuploads%2F7jrN1kxjCn5BoxQIgkHf%2Fimage.png?alt=media&amp;token=ca53dcd0-4727-4883-a4e3-b34424d8be36" alt="Graph with alarm and warning limits"><figcaption><p>Alarm and warning limits on a graph</p></figcaption></figure>

### Warning vs alarm

* **Warning**
  * Indicates values outside normal range, but still acceptable.
  * Closes automatically when readings return within limits.
  * Usually does not require immediate intervention.
* **Alarm**
  * Indicates values outside allowed range.
  * Requires immediate attention.
  * Remains active until signed.

{% hint style="info" %}
Both warnings and alarms use [Alarm Filter](/boomerang-3-user-manual/dashboard/alarms_and_warnings/alarm-filter.md) to require consecutive out-of-limit readings.
{% endhint %}

### Time-of-day schedules

Limits can be valid only during specific times of day.

Use this to ignore expected deviations (for example, defrost cycles).


---

# 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://help.boomerang3.com/boomerang-3-user-manual/dashboard/alarms_and_warnings/alarm-limits.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.