> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/licensable-features/advanced-alarm-management-feature/reactivation-restoral-behaviour-with-new-triggers.md).

# Reactivation/Restoral behaviour with new triggers

Alarm restorals and reactivations do not originally factor into notifications with triggers of 'before acknowledgement' and 'after acknowledgement', as only acknowledgement and process alarm actions affect its timers.

If the **Include Alarm Restorals** checkbox is ticked on the **Triggers** tab of the Notification Filter properties, an alarm that has its timer activated for "not acknowledged" will have no behaviour changes. However, if this notification has already been sent, and the alarm changes states without being acknowledged still, the timer will restart.

The intention of this is to send a reminder message if the alarm is still 'active' and changing states but have not been addressed. A similar behavior happens if the alarm is acknowledged for too long.


---

# 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.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/licensable-features/advanced-alarm-management-feature/reactivation-restoral-behaviour-with-new-triggers.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.
