> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/alert-center/alarms/acknowledgment-obligation-and-dismissed-alarms.md).

# Acknowledgment Obligation and Dismissed Alarms

## Overview

### What are dismissed alarms?

An alarm is "dismissed" when the criteria for an alarm are no longer met and it is not an alarm subject to acknowledgment.

A dismissed alarm no longer appears in the Alarm Overview. However, a dismissed alarm always appears in the [↗ Alarm History](/collection/platform/alert-center/alarms.md#alarm-history).

Alarms CANNOT be deleted from the Alarm History.

### What are alarms subject to acknowledgment?

Alarms subject to acknowledgment appear in the [↗ Alarm Overview](/collection/platform/live-cockpit/widgets/predefined-widgets/alarm-overview.md) until they are acknowledged by a user.

After an alarm subject to acknowledgment has been acknowledged, the alarm is moved to the [↗ Alarm History](/collection/platform/alert-center/alarms.md#alarm-history).

Whether an alarm is subject to acknowledgment is configured in the [↗ rule](/collection/platform/alarms-rules-and-escalations/rules.md) that triggers the respective alarm. Alarms subject to acknowledgment are highlighted by a marker **\[B]**.

{% hint style="info" %}
**Example 1**

A rule is created that triggers an alarm as soon as the temperature drops below 20 °C. The rule is marked as *not subject to acknowledgment*.

* The temperature drops below 20 °C\
  ▷ An alarm is triggered\
  ▷ The alarm appears in the Alarm Overview
* The temperature rises back above 20 °C\
  ▷ The alarm "Dismisses"\
  ▷ The alarm no longer appears in the Alarm Overview\
  ▷ The alarm appears in the Alarm History

**Example 2**

A rule is created that triggers an alarm as soon as the temperature drops below 20 °C. The rule is marked as *subject to acknowledgment*.

* The temperature drops below 20 °C\
  ▷ An alarm is triggered\
  ▷ The alarm appears in the Alarm Overview\
  ▷ The alarm is marked as subject to acknowledgment **\[C]**
* The temperature rises back above 20 °C\
  ▷ The alarm does not "Dismiss"\
  ▷ The alarm remains visible in the Alarm Overview
* The alarm is acknowledged\
  ▷ The alarm no longer appears in the Alarm Overview\
  ▷ The alarm appears in the Alarm History
  {% endhint %}

<figure><img src="https://3489494878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9GvUpaatBiReR43XFSMg%2Fuploads%2FPTPLFtmAuzSz3C6D4leW%2FDocs_Alarme%201.png?alt=media&#x26;token=7b28ad6c-5309-4a1f-96b2-ba276c91a5b3" alt=""><figcaption></figcaption></figure>

## Acknowledge an Alarm

1. Open the [↗ Alarm Overview](/collection/platform/live-cockpit/widgets/predefined-widgets/alarm-overview.md)
2. Click on **\[M]** for the desired alarm\
   ▷ The menu **\[M1]** opens
3. Click on **\[M6]**\
   ▷ The alarm is acknowledged

## Acknowledge an Alarm with a Comment

1. Open the [↗ Alarm Overview](/collection/platform/live-cockpit/widgets/predefined-widgets/alarm-overview.md)
2. Click on **\[M]** for the desired alarm\
   ▷ The menu **\[M1]** opens
3. Click on **\[M7]**
4. Enter a comment and click OK.

### Logbook

If an alarm has already been acknowledged with a comment, the "Logbook" option appears instead of **\[M7]**. The comment that was entered when an alarm was acknowledged with a comment is displayed in the logbook.


---

# 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.buildings.ability.abb/collection/platform/alert-center/alarms/acknowledgment-obligation-and-dismissed-alarms.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.