> 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-signing.md).

# Alarm signing

Sign alarms after corrective action to close them.

Alarms remain **active** until a user signs them.

Warnings close automatically when the alarm condition disappears.

{% hint style="warning" %}
Do corrective actions before signing.

If the condition persists, the alarm can trigger again after signing.
{% endhint %}

{% stepper %}
{% step %}

### Open the alarm list

On the Dashboard, click the [Measuring Points button](/boomerang-3-user-manual/dashboard/dashboard-buttons/measuring-points-button.md).

<figure><img src="https://content.gitbook.com/content/EANwXRnuP0ug8971viyg/blobs/o9yF8p5eySXoxAw7VLo1/image99.png" alt="Organisation tree showing active alarms"><figcaption><p>Active alarms in groups</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/EANwXRnuP0ug8971viyg/blobs/FAhi18s8jgufOi6DnKVX/image100.png" alt="Measuring point alarms list"><figcaption><p>Alarm list</p></figcaption></figure>
{% endstep %}

{% step %}

### Select alarms

* Select all using the checkbox in the header.

<figure><img src="https://content.gitbook.com/content/EANwXRnuP0ug8971viyg/blobs/E1yL3TSpfNtuiI4UbBNk/image101.png" alt="Select all alarms checkbox"><figcaption><p>Select all alarms</p></figcaption></figure>

* Or select individual alarms.

<figure><img src="https://content.gitbook.com/content/EANwXRnuP0ug8971viyg/blobs/LGh3bFCNZEMiwjsisg1g/image102.png" alt="Select one alarm checkbox"><figcaption><p>Select an alarm</p></figcaption></figure>
{% endstep %}

{% step %}

### Sign

1. Click **Sign Alarm**.
2. Add a comment.
3. Sign the action.

Signing is described in [Sign](/boomerang-3-user-manual/common_elements/sign.md).

<figure><img src="https://3588014471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEANwXRnuP0ug8971viyg%2Fuploads%2Fuft7tFvZyLuxMJmFbPZT%2Fimage.png?alt=media&amp;token=4f980840-e299-4588-8f98-54bcc8d2d947" alt="Sign Alarm dialog with comment"><figcaption><p>Sign Alarm</p></figcaption></figure>
{% endstep %}

{% step %}

### Check the result

Signed alarms disappear from the active list.

<figure><img src="https://content.gitbook.com/content/EANwXRnuP0ug8971viyg/blobs/DGCz0dhaV9GzqCZUS7nN/image104.png" alt="Active list after signing"><figcaption><p>Active list after signing</p></figcaption></figure>
{% endstep %}

{% step %}

### Verify in history

Signed alarms remain visible in the object’s [Activity log tab](/boomerang-3-user-manual/dashboard/object_view/detailed-object-view/activity-log-tab.md) when you filter to **All**.

<figure><img src="https://3588014471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEANwXRnuP0ug8971viyg%2Fuploads%2FfrlAcEKFLHAnfZMmgT7x%2Fimage.png?alt=media&amp;token=bed2eedc-f4d8-4591-b399-4a0d9b52970d" alt=""><figcaption><p>Signed alarms in history</p></figcaption></figure>
{% endstep %}

{% step %}

### Warnings

Warnings are automatically signed when the reading returns within limits.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
You can also sign active alarms in the object view, from the Activity log tab.
{% endhint %}


---

# 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-signing.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.