Dashboard trend — the data-points table says it could not load
Under a failed history read, the table stops claiming the range is empty
28 Sept 2026 · branch dashboard-stats-strip-says-when-the-read-failed · captured against propflow-stage · at 9dc3a54184+local
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · The history read fails: the chart AND the table say they could not load
The metric-history request is aborted in this browser. The chart says Couldn't load this trend (#13064), and the table under it now says Couldn't load these data points instead of "No data points in range."
Asserted in the captured DOM — Couldn't load this trend · Couldn’t load these data points
2 · Control: the read allowed, this fixture's history is genuinely empty
Nothing blocked: the read lands with no points, so both the chart and the table keep saying the range is empty. That is the true claim for a read that landed.
Asserted in the captured DOM — No data for this range · No data points in range.
