> 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/english-v14/documentation/alarme-regeln-und-eskalationen/alarme/quittierpflichtige-und-gehende-alarme.md).

# Acknowledgement-required and ongoing alarms

## Overview

### What are cleared alarms?

An alarm "goes" when the criteria for an alarm are no longer met and it is not an alarm that requires acknowledgment.

A cleared alarm no longer appears in the alarm overview. However, a cleared alarm always appears in the [↗ alarm history](/collection/english-v14/documentation/alarme-regeln-und-eskalationen/alarme.md#alarm-historie).

Alarms cannot be deleted from the alarm history.

### What are acknowledgment-required alarms?

Acknowledgment-required alarms appear in the [↗ alarm overview](/collection/english-v14/documentation/alarme-regeln-und-eskalationen/alarme.md#die-alarm-uebersicht), until they have been acknowledged by a user.

After an acknowledgment-required alarm has been acknowledged, the alarm is moved to the [↗ alarm history ](/collection/english-v14/documentation/alarme-regeln-und-eskalationen/alarme.md#alarm-historie)history.

Whether an alarm requires acknowledgment is configured in the [↗ rule](/collection/english-v14/documentation/alarme-regeln-und-eskalationen/regeln.md) configured by which the respective alarm is triggered. Acknowledgment-required alarms are highlighted by a marking **\[B]** highlighting.

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

A rule is created that triggers an alarm when the temperature drops below 20 degrees. The rule is set as *not acknowledgment-required* .

* The temperature drops below 20 degrees\
  ▷ An alarm is triggered\
  ▷ The alarm appears in the alarm overview
* The temperature rises back above 20 degrees\
  ▷ The alarm "goes"\
  ▷ 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 when the temperature drops below 20 degrees. The rule is set as *acknowledgment-required* .

* The temperature drops below 20 degrees\
  ▷ An alarm is triggered\
  ▷ The alarm appears in the alarm overview\
  ▷ The alarm is marked as acknowledgment-required **\[C]** tagged
* The temperature rises back above 20 degrees\
  ▷ The alarm "does not go"\
  ▷ 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://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/m6CnbkoenfJGOwRErgF0/Docs_Alarme%201.png" alt=""><figcaption></figcaption></figure>

## Acknowledging an alarm

1. Go to the [↗ alarm overview ](/collection/english-v14/documentation/alarme-regeln-und-eskalationen/alarme.md#die-alarm-uebersicht)on
2. Click on the desired alarm on **\[M]**\
   ▷ The menu **\[M1]** opens
3. Click on **\[M6]**\
   ▷ The alarm is acknowledged

## Acknowledging an alarm with comment

1. Go to the [↗ alarm overview](/collection/english-v14/documentation/alarme-regeln-und-eskalationen/alarme.md#die-alarm-uebersicht) on
2. Click on the desired alarm on **\[M]**\
   ▷ 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, instead of **\[M7]** the option "Logbook" appears. In the logbook, the comment that was entered when an alarm was acknowledged with comment is displayed.

##


---

# 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/english-v14/documentation/alarme-regeln-und-eskalationen/alarme/quittierpflichtige-und-gehende-alarme.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.