RMQ002 — a query failed and nothing rendered it

The query is in error, and the render that just happened read none of isError, error, status or result. The report names the key and the failure.

It matters because a failed refetch keeps the data it had: the page can look perfectly healthy while showing values that no longer refresh. Nothing throws, nothing is blank, and the only sign is that a number stopped moving.

This is the answer to throwOnError, which @ramonda/query does not have. What that option is really for is noticing, and noticing is a development-time report — where rethrowing into an error boundary would unmount the subtree, run every cleanup, and throw away local state, focus and scroll for something as ordinary as a timeout.

Reading any one of those four silences it, per render: a component that showed the error and then stopped (a collapsed panel, a switched tab) is reported again, because each render is judged on its own reads.

Next

• All diagnostics — every code the framework can report.
• Checking your app — the faults proved from the source, before anything runs.