> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/protect-your-locations-with-alarms/use-and-configure-alarms/alarm-schedule-exceptions.md).
# Alarm Schedule Exceptions
Configure exceptions to your alarm schedule.
You can create **Schedule Exceptions** so that the alarm system is armed or disarmed during a period of time not defined in your current alarm schedule.
This feature is intended to make it easier to change the alarm schedule for a specific day (or days), but keep the existing alarm schedule in place outside of the exception.
**Note**: If you have [temporarily armed](/docs/protect-your-locations-with-alarms/use-and-configure-alarms/arm-and-disarm-alarms.md#arm-temporarily) the alarm system, the temporary arm takes priority and any scheduled exceptions are ignored. You must resume the alarm schedule or wait for the temporary arm to finish to ensure alarm schedule exceptions are followed.
Here are some examples of how you can use alarm schedule exceptions:
* **Holidays**: If your location is closed for a holiday, you can configure an alarm schedule exception to **arm the system for the entire length of the holiday** without changing your existing alarm schedule. For example, the holiday is the length of an entire Friday and you want to ensure the alarm is armed on this Friday, but your alarm schedule is set to disarm your alarm from 8 A.M. to 6 P.M. on Fridays; with an alarm exception, you can choose to arm the system for the entire length of this specific Friday and override your current alarm schedule.
* **Special Events**: Your location usually closes at 6 P.M. on Fridays, but is hosting an event until 9 P.M. on a specific Friday; you can create an alarm exception to keep the alarm disarmed until after 9 P.M. on that day.
* **Renovations**: You may need to disarm the alarm system during renovation periods. You can set as many alarm exceptions as needed to ensure the system is disarmed during renovation times.
***
### Add Schedule Exception
To add an alarm schedule exception:
1. From the **Alarms** page, select a location you would like to configure an alarm schedule exception for:
2. Select **Add Schedule Exception**:
3. Select which alarm camera(s) you want to include:
4. Select a **Start** and **End** date and time for the exception. The Start time is the exact time the exception begins and the End is the time the exception ends:
**Note:** Take note of the **Duration** - this displays the length of time the exception will be in place. Also take note that the configured time corresponds to the location's local time zone.
5. Choose how often this exception repeats based on the available options:
6. Type a **Title** and **Description** for the exception. These appear in the alarm schedule exception area on the Alarms page once you save it (to help you reference the exception later). You could name the exception "Holiday" for example.
7. Choose to **Arm** or **Disarm** the alarm during the period of time you have specified for the exception:
8. Select **Save** to create the exception.
Once you create the alarm schedule exception, you can review, edit and/or delete it via the "more options" menu (three dots):
To add additional alarm exceptions, select the **Add** button:
Watch the following video tutorial for more information on how to configure alarm schedule exceptions:
{% embed url="" %}
\
\
---
# 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.solink.com/docs/protect-your-locations-with-alarms/use-and-configure-alarms/alarm-schedule-exceptions.md?ask=&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.