> 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/configuration-client/site-management/reports/creating-a-new-report/exception-report.md).

# Exception Report

### Introduction

The Exception Report allows operators to generate a list of exceptions to the normal system operation, (i.e. outstanding issues such as unprocessed alarms).

This report may be generated by an operator at the start of their shift, to obtain an overview of the system's current status. They request an Exception Report on the division for which they have responsibility immediately after logging onto the system.

Operators must have the "Edit Report Descriptions" privilege to create, save, edit and delete Exception Reports.

This report can be scheduled to run automatically at regular times (via Action Plans or scheduled Macros). For further information refer to [Automatically Generated Reports](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/automatically-generated-reports.md) and [Configuring Report Scheduling](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/automatically-generated-reports/configuring-report-scheduling.md).

***

### Report Wizard

The Exception Report wizard contains a number of pages which prompt you to enter certain information to create a report.

**Follow the instructions displayed.**

<details>

<summary>Report Style page</summary>

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a3748440e22316cfeb6fd0cdf2c6eb7f126f6908%2Fexceptionrpt_1.png?alt=media)

This is the first page of the Exception Report wizard. It allows the operator to select either an **Unprocessed Alarms Report**, or an **Unlocked Doors Report**.

**Unprocessed Alarms Reports** include all unprocessed alarms, whether or not they are acknowledged. For this option to be enabled, an operator needs the “View Events and Alarms” or the “Edit Alarms” operator privileges.

**Unlocked Doors Reports** include all doors that are scheduled to be secure but are currently unlocked because of an override or an active alarm condition related to the door. This report is split into the following two sections:

* **Override section:**\
  This section of the report lists doors that are scheduled to be secure, but are currently in 'Free' mode.\
  **Note:** If a door has two zones (one entry zone and one exit zone), both zones need to be overridden to 'Free', otherwise the door will remain 'secure'.
* **Active Alarms section:**\
  This section of the report lists doors with any of the active alarms:
  * Forced Door
  * Door Not Locked
  * Door Open Too Long
  * Door Emergency Release

For the 'Unlocked Doors Report' option to be enabled, an operator needs either the “View Site” or “Edit Site” operator privileges. This allows them to run the report, but they will only be able to view the Override section. They also require the "View Events and Alarms" operator privilege to view the Active Alarms section of the report.

**Note:** A secure door will not be listed as unlocked simply as a result of a cardholder opening the door temporarily to gain access at the time the report performs its checks.

You can optionally **Schedule this report to run at specified times** for both report styles.

</details>

<details>

<summary>Regional Settings page</summary>

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4739ae0a524294dee7b82fb989393bd9fb23f960%2Fexceptionrpt_2.png?alt=media)

This page allows a time zone and/or language to be selected for the report. Selection of a time zone is optional, as it is only required for Command Centre sites that span time zones. Selection of a language is also optional as it is only required for sites that have multiple languages.

If no time zone is selected, the report uses the time zone of the Command Centre server, only if the report was initiated from a macro which was triggered by an Action Plan, or a macro that was run from its schedule. In all other cases, the report uses the time zone on the workstation of the operator who has run the report, or the time zone on the workstation of the operator who ran the macro that triggered the report.

If a time zone is selected, when the report is run, all dates and times within the report will display in the selected time zone. Any dates and times configured within the report are assumed to be within the selected time zone (rather than the time zone on the configuring operator's workstation).

</details>

<details>

<summary>Report Scheduling page</summary>

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1b161bd36b7a3bdb65a181554e676655e6c588c8%2Fexceptionrpt_3.png?alt=media)

This page only displays if the "Schedule this report to run at specified times" checkbox is checked on the **Report Style** page. It allows run times and repetition properties to be defined for the report.

Multiple explicit times for the report to be run can be configured, as follows:

1. Click the **Run at** radio button.
2. Enter a date and time, and click the **Add** button.

   The date and time appears in the **Next Scheduled Run Times** grid.
3. Repeat Steps 1-2 for each explicit time you require.

   **Note:** If you click the **Repeats** radio button, then the explicit additions are removed from the **Next Scheduled Run Times** grid.

Repeat times for the report to be run can be configured, as follows:

1. Click the **Repeats** radio button.
2. Select the 'initial' **From** date and time.
3. Select an **Until** date and time if required.

   **Note:** If no **Until** date is entered, the report will repeat indefinitely.
4. Select the regularity for the report to be run, (i.e. **Every** one or many **Hours**, **Days**, **Weeks** or **Months** ).

   **Note:** When **Weeks** is selected from the drop-down list, the days of the week display with an ability to select one or multiple days, (e.g. Monday and Thursday).

   The next five dates and times appear in the **Next Scheduled Run Times** grid.

The **Division** selection grid allows the report to be scheduled for specific divisions.

**Note:** Only Divisions to which you have the appropriate editing privilege will appear in the drop-down list.

</details>

<details>

<summary>Report Generation and Saving page</summary>

This wizard page is the same for all report types, and provides the same options. Refer to [Report Generation and Saving](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report.md) in the *Creating a new report* procedure for further detail.

</details>


---

# 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/configuration-client/site-management/reports/creating-a-new-report/exception-report.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.
