Alerts & Incidents
How Cassian™ tells you when something is wrong — the incident centre, alert lifecycle, quiet hours, and sensitivity controls.
Cassian™'s job is telling you when something is wrong with your store. Every monitor — uptime, orders, pricing, stock, security, and more — feeds into a single incident queue, so there is one place to look when something needs your attention: the Alerts page at Dashboard → Alerts.
The Alerts Page
The Alerts page is your incident centre. It shows every open incident across every monitor, most urgent first, along with a delivery log of the notifications Cassian™ has sent. Each incident shows what was detected, when, how severe it is, and — where Cassian can estimate it — the dollar impact.
Incident Lifecycle
Every incident moves through a simple lifecycle:
| Status | Meaning |
|---|---|
| Open | Detected and unresolved. This is what needs your attention. |
| Acknowledged | You've seen it and you're on it. Cassian won't notify you about it again. |
| Snoozed | Muted until a time you choose. It returns to open when the snooze elapses. |
| Resolved | The underlying condition cleared — either Cassian confirmed recovery, or you resolved it. |
Acknowledging or snoozing an incident suppresses further notifications for it. The incident stays visible on the Alerts page, so nothing silently disappears.
What Feeds the Queue
Nine monitor sources open incidents in the same queue:
| Source | What it watches |
|---|---|
| Uptime Monitoring | Store availability, response time, SSL and domain expiry |
| Order Pulse | Order flow anomalies — zero-order events, drops, declines |
| Pricing Pulse | $0 prices, inverted sales, unexpected price changes |
| Stock Monitor | Stock-outs and projected low-stock (WooCommerce & BigCommerce) |
| Security Scanning | Cassian Shield™ findings — headers, SSL/TLS, vulnerabilities |
| Link Checker | Broken links appearing on your store |
| Sitemap Monitoring | Pages disappearing from or flooding into your sitemap |
| PageSpeed Monitoring | Lighthouse score regressions |
| Scans | Critical findings from your scheduled Cassian AI™ scans |
Severity Levels
Every incident carries a severity: critical, warning, or info. Severity drives everything downstream — which channels are notified, whether quiet hours apply, and how prominently the incident appears.
Quiet Hours
Quiet hours keep non-urgent alerts from waking you. When enabled, the default window is 22:00–07:00 in your organisation's timezone (both are adjustable).
- Warning and info alerts detected during quiet hours are held and delivered when the window ends.
- Critical alerts always break through — if your store goes down at 3 AM, you'll know at 3 AM.
Per-Channel Severity Floors
Each notification channel (email, Telegram, webhook) can have its own minimum severity. For example: everything to email, but only critical alerts to Telegram. The default floor is info — every alert goes to every enabled channel until you say otherwise. See Notifications for channel setup.
Sensitivity Presets
Each monitor can be tuned per site with one of three presets:
| Preset | Behaviour |
|---|---|
| Relaxed | Fewest alerts — only the most significant changes fire |
| Normal | Cassian's standard thresholds — the default every store starts with |
| Sensitive | Earliest warning — smaller changes fire, more alerts |
The thresholds quoted on each feature's documentation page are the Normal defaults. Presets are set per site, per monitor, so you can run Pricing Pulse on Sensitive while keeping PageSpeed on Relaxed.
The Delivery Log
The Alerts page includes a delivery log showing your last 50 notification attempts — which channel, which incident, whether it was delivered, and if not, why (for example, held for quiet hours or below a channel's severity floor). If you think an alert should have arrived and didn't, this is the first place to look.
Where to Configure
Alert configuration lives in the Alert controls section of Settings (organisation admins only):
Go to Settings and find Alert controls.
Enable and set your quiet hours window if you want one.
Set sensitivity presets per site and per monitor.
Set per-channel severity floors for email, Telegram, and webhooks.
Channel setup itself (adding Telegram, configuring webhooks) lives in Notifications.
Frequently Asked Questions
I acknowledged an incident — will I be told when it's resolved? Recovery notifications depend on the monitor. Uptime sends a "back up" notification; some monitors (like Stock Monitor) resolve silently. Acknowledging never blocks a recovery notification — it only stops repeat alerts for the same ongoing incident.
Why didn't I get an alert I expected? Check the delivery log on the Alerts page. Common reasons: the alert fired during quiet hours (warning/info are held), it was below a channel's severity floor, or the incident was already open and acknowledged.
Do sensitivity presets change what Cassian detects, or just what it sends? They change detection thresholds themselves — on Relaxed, smaller changes aren't classified as incidents at all.
Can different team members have different alert settings? Alert configuration is per organisation and per site, not per user. Notification channels are also organisation-level.