The usual assumption: when an agent checks an order's status, sees active , and ships an order the customer cancelled a second earlier, the model hallucinated. Fix the prompt.
In a lot of transactional workflows that's the wrong layer. The cancellation committed on the primary. The agent's tool read from an async read replica that hadn't applied it yet. The model reasoned correctly over a row that was already out of date.
Sending agent, RAG and tool traffic to replicas is a sensible way to protect the primary. Fine for dashboards. For anything that reads a row and then acts on it, it's a trap: a human double-checks a stale dashboard, an agent just acts.
Why lag shows up as bad reasoning
With async replication the primary confirms the write first and ships it to replicas afterwards. Until a replica applies it, reads there return the old value. AWS says Aurora replica lag is usually well under 100 ms, but it grows under heavy writes.…