Troubleshooting
What to do when a store has an unexpected change, a change fails, or something looks wrong, and what keeps running when something else breaks.
Most day-to-day issues fall into one of two buckets: a store has an unexpected change that nobody asked for, or a change didn't work the way you wanted. In both cases, Reqursor Platform shows you what changed, where it changed, and how serious it is, rather than leaving you to guess. This section walks through how to read that evidence and decide what to do next.
More on this section is coming
Troubleshooting guides (starting with reading a report of unexpected changes and deciding whether to redeploy or investigate) are on the way.
What data reaches the LLM
An exact, agency-facing statement of what store information is sent to the AI provider that powers Reqursor's intelligence, and what is never sent, no exceptions.
Design Decisions
Why Reqursor works the way it does: the reasoning behind decisions like no autonomous remediation and a mandatory preview-and-confirm gate.