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.
Fixing an unexpected change (a change nobody asked for) once is straightforward. But if the same problem keeps coming back, blindly applying the same fix every time would hide something worse: usually, an ongoing cause outside Reqursor. Reqursor watches for that pattern specifically, not just for single incidents.
Three patterns Reqursor watches for
| Pattern | What Reqursor notices | What it does |
|---|---|---|
| The same change, same store, soon after being fixed | The identical mismatch reappears not long after a successful fix | Instead of putting the saved setup back blindly again, it flags that something outside Reqursor is likely undoing the fix, and asks how you want to handle it |
| The same change, across a group of stores | Multiple stores in the same group show the identical mismatch | It points to a shared cause, like an update to all your stores that didn't apply as expected, rather than treating each store as its own unrelated incident |
| Unexpected changes piling up on one store | A single store picks up unexpected changes in several areas over a short period | It treats this as a sign the store is actively being changed outside Reqursor, not a string of coincidences |
What this actually looks like
Each pattern produces a specific, plain-language message rather than a repeat of the same generic alert:
- Same store, recurring: "Store X has the same unexpected change again. Something outside Reqursor is changing this setting. Do you want to investigate the outside change, put the saved setup back again, or pause checking this specific setting for now?"
- Across a group: "5 stores in the Fashion group all show the same plugin version mismatch. This may be from an update that didn't apply cleanly. Do you want to undo the update on all 5 and go back to their previous version?"
- Piling up on one store: "Store X has picked up unexpected changes in 3 different areas over the past day. This suggests the store is being changed outside Reqursor. Do you want to reapply everything Reqursor manages for this store?"
Why Reqursor asks you instead of repeating the fix
Applying the same fix over and over without noticing the pattern would hide a real, ongoing problem, like something outside the platform overwriting a setting every single time, instead of resolving it. Recognizing the pattern lets the AI ask the right question the second or third time, rather than quietly repeating the same fix forever.
Why this matters for your agency
- Recurring problems get named as recurring, not re-reported as if they're new each time.
- Causes shared by many stores are caught early: one shared reason is presented as one issue to solve, not five separate alerts.
- You're asked before Reqursor keeps trying the same thing: repeated fixes that don't work don't happen silently in the background.
Where to go next
Understanding unexpected changes
The monitoring across all your stores that this pattern spotting builds on.
How Reqursor fixes unexpected changes with AI
The normal version for a one-off change, which this page builds on.
Fixing unexpected changes from the dashboard or in chat
Where you'd see and respond to a message like these.
How Reqursor fixes unexpected changes with AI
The full flow from an unexpected change being spotted to an AI diagnosis, a proposal, your confirmation, and the fix going live.
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.