How Can We Help?
Polar Cloud
- Action Buttons
- Adding Alerts
- Adding Users
- Adding Users to Alerts
- Alert Action Triggers
- Alert Types
- Calculated Fields
- Can I change my login details ?
- Configure a 4–20mA sensor reading
- Configure a pulse water meter
- Create a conditional alert with several thresholds
- Device Dashboard
- Download Polar App on your phone
- Editing Users
- First Time Setup
- Groups
- Home Screen Navigation
- How do I get my login details?
- How to edit a users account details
- Poll Rates
- Read connection status and Site licence usage
- Remote Programming
- Removing A User
- Schedulers
- Sites
- Software License
- User Roles
- Viewing Active Alerts
- Viewing Historical Alerts
- What happens during an internet or power outage?
- What happens to schedules and alerts during an outage?
- Show all articles (16) Collapse Articles
What happens to schedules and alerts during an outage?
| Execution mode | During network disconnection | After reconnection |
|---|---|---|
| Cloud scheduler, including LTE/Ethernet | Cannot deliver the control through the disconnected gateway. The scheduled action fails/is lost. | No replay of the missed action; wait for the next scheduled occurrence. |
| Cloud measurement alert | Cannot evaluate new device readings that are not reaching the cloud. The separately configured Gateway Offline alert can still detect missing device DB records. | Evaluation resumes with available readings. If the trigger condition is met, the alert can trigger then. For example: below-30% tank alert, level 25% when communication returns. |
| Glacier scheduler set to edge | Continues locally while the required equipment remains powered and licensed; stores local data. | Local stored data synchronises. Do not apply the missed-cloud-action rule to a schedule that actually executed locally. |
| Glacier locally enabled alert | Can evaluate locally and retain the event timestamp. Notifications cannot be sent through the cloud while disconnected. | Sends the delayed alert after cloud connectivity returns, retaining the timestamp of when it triggered locally. |
A delayed Glacier edge notification may describe an earlier event. Distinguish the recorded event time from the time the customer receives the message. Delivery uses the cloud; Glacier can evaluate locally when local alerts are enabled.
Cloud-only evaluation does not reconstruct a short event for which no readings reached the cloud. If the reading is still beyond the threshold after reconnection, normal cloud evaluation can trigger the alert. An alert sends one trigger notification and one resolve notification. There are no recurring reminders or acknowledgement controls.
Table of Contents