---
title: "Troubleshoot alarms"
canonical: "https://help.scopious.co.nz/space/KB/164036609/Troubleshoot%20alarms"
format: markdown
---
> Macro (toc)

## Not Receiving Notifications

1. Check that the state of the Alarm has changed. If it has not changed, then nothing will be sent.
2. Double-check your Alarm configuration. Carefully read through your rules and conditions to ensure that the state will change when expected. You can validate this using the **Validate** button in the top left of the Alarm page.
3. Double-check your Alarm Notification settings ensuring the correct recipients have been specified.

### Not Receiving Email Notifications

1. Check conditions above.
2. Check your spam/junk folders. Sometimes email providers might automatically send the email to the spam/junk folder, especially if you are receiving many notification emails.

### Not Receiving In-App Notifications

1. Check conditions above.
2. Ensure the Scopious application is open. If the application was closed when the alarm was notified, you can view the notification by opening the application and clicking on the notification bell at the top right of the screen.

> ℹ️ Note InApp notifications are different to Push notifications. InApp notifications can only be alerted when the application is open. Push notifications can alert even when the application is closed. We currently do not support Push notifications.

## Faulty Alarm Configuration

> ℹ️ An alarm that was once working may become faulty if devices in your network are updated or removed. Faulty alarms can be identified by the flashing red exclamation mark when viewing alarms in the Control Centre.

To identify and diagnose faulty alarms:

1. Navigate to the **Control Centre** page using the navigation menu on the left side of the screen.
2. Look for alarms with a flashing red exclamation mark.
3. Click on the title of the alarm to open it.
4. Click the Conditions tab in each Rule to see if it contains a faulty configuration.
5. Once the faulty condition is identified, reconfigure it and test it.

![Faulty Alarm.gif](media://17a0bfe5-9191-4367-a1aa-1a02ab0e20ca)