When unexpected changes trigger an alert
The exact thresholds behind Reqursor's alerts: high severity, unexpected changes lasting over an hour, multiple stores affected, stale checks, and patterns that keep returning.
Understanding unexpected changes explains the kinds of alerts Reqursor sends. This page gives the exact thresholds behind each one.
The thresholds
| Alert | Default threshold | What you see |
|---|---|---|
| High-severity unexpected change on any store | Zero tolerance: flagged the moment it's detected | Immediate notification, with an AI-proposed fix |
| A store with unexpected changes for a while | Over 1 hour | Surfaced in your daily digest as worth reviewing |
| Many of your stores with unexpected changes | More than 10% of your stores | Flagged as a possible issue affecting multiple stores, not just one-off problems |
| A store's check running late | More than twice its normal interval | Marked as "check stale," so you know its status might not be current |
| The same unexpected change returning after a fix | Reappears twice | Flagged as a recurring pattern: see Spotting unexpected changes that keep coming back |
Defaults, not fixed rules
These are the platform's default thresholds. Production stores are watched more closely than staging or development ones by default: see Understanding unexpected changes for the checking schedule behind that.
Why this matters for your agency
- You know exactly what triggers an alert, not just a vague sense of "sometimes Reqursor tells me things."
- Severity is proportional. A single store with a small problem and multiple stores with an issue don't compete for your attention the same way.
- Nothing waits for you to notice it. Every threshold above is checked automatically, on every store, all the time.
Where to go next
Understanding unexpected changes
The kinds of alerts Reqursor sends, and how checking works overall.
How store health is checked
How the health status you see is actually determined.
Spotting unexpected changes that keep coming back
What happens after Reqursor detects an unexpected change more than once.
Spotting unexpected changes that keep coming back
How Reqursor recognizes when the same unexpected change keeps happening, on one store or across a group, and asks you instead of repeating the same fix blindly.
How store health is checked
How the healthy, degraded, unexpected change, failing, and unknown statuses are actually determined for each store.