Why changes made outside Reqursor are caught
Why editing a store directly, outside Reqursor, is always treated as an unexpected change, never as a new saved setup.
Sometimes someone touches a store directly: updates a plugin from the store's admin area, tweaks a setting by hand, connects to the server itself. Whatever the reason, Reqursor's rule is absolute: a change made outside Reqursor is an unexpected change (a change nobody asked for). It is never quietly accepted as the new plan.
Why the saved setup always wins
Reqursor recognizes exactly one official answer for what a store should look like: its saved setup on record, called its declaration (see Core concepts). What's actually running is just what's observed: useful for checking against the saved setup, but never the final word. If the two disagree, the saved setup is correct and the running store has changed unexpectedly. Never the other way around.
This means a change made outside Reqursor doesn't become the new official setup just because it's live. If someone updates a plugin outside Reqursor, the saved setup hasn't changed; Reqursor's next check simply reports the plugin version as an unexpected change in the right area.
What happens next
A change made outside Reqursor gets exactly the same treatment as any other unexpected change: the AI reads the evidence and proposes what to do next. There are two paths, and both need your confirmation:
- Put the saved setup back: undo the outside change and bring the store back in line with what's on record.
- Update the saved setup to match: if the outside change should stay, make it official by adding it to the store's saved setup going forward.
Neither happens automatically. See How Reqursor fixes unexpected changes with AI for how that proposal reaches you.
Why this rule matters
Without it, "what does this store actually look like" would depend on whoever touched it last: word of mouth instead of a single record everyone, including the AI, can trust.
Why this matters for your agency
- There's always one answer to "what should this store be?": never a guess based on who changed what, when.
- Nothing made outside Reqursor slips through unnoticed. Even a well-intentioned quick fix gets surfaced, not silently absorbed.
- You choose how an outside change gets resolved (undone or made official) instead of the platform deciding for you.
Where to go next
How Reqursor confirms a store is set up as intended
The exact conditions a store has to meet to count as matching its saved setup.
Understanding unexpected changes
How Reqursor catches changes like this automatically, on a schedule.
How Reqursor fixes unexpected changes with AI
What happens between an outside change being spotted and it being resolved.
Operate
Keeping every store in your portfolio healthy day to day: health monitoring, spotting unexpected changes, and AI-suggested fixes across all your stores.
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.