> 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/products/cc-software/troubleshoot/command-centre-errors/server-asserts-when-a-macro-processes-alarms.md).

# Server asserts when a macro processes alarms

Resolve server asserts that occur when a macro processes alarms without an Alarm Zone field.

**Symptom:** the server asserts when alarms are processed via a Macro and the alarm source does not have an Alarm Zone field.

**Affected versions:** v8.00.1252 MR7, v8.10.1253 MR6, v8.20.1218 MR4, v8.30.1299 MR2, v8.40.1252 Full Release.

**Cause:** one of the fixes implemented in the versions above caused this anomaly. It only affects sites that use a Macro to process alarms in Command Centre.

{% hint style="info" %}
This assert only happens if you are using a Macro to process alarms and an alarm with no alarm source exists in the Alarm Viewer at the time of processing. Example: a Command Centre generated alarm, such as a report that failed.
{% endhint %}

**Workaround:**

* Do not use a Macro to process alarms.
* Turn off Assert dumps if using Macros, but this is not ideal.

**Fix :** Fixed in v8.00 MR8+, v8.10 MR7+, v8.20 MR5+, v8.30 MR3+ and v8.40 MR1+.


---

# 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/products/cc-software/troubleshoot/command-centre-errors/server-asserts-when-a-macro-processes-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.
