Dashboard trend — a failed history read says it could not load
A failed read and a quiet period stop looking the same
28 Sept 2026 · branch dashboard-trend-read-failure-says-so · captured against propflow-stage · at 70d12d07fb+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 trend says it could not load
The metric-history request is aborted in this browser, the same path as a thrown fetch. The expanded occupancy trend says Couldn't load this trend instead of "No data for this range".
Asserted in the captured DOM — Couldn't load this trend · Refresh the page to try again.
2 · Control — the same page with the read allowed: an empty history still says there is no data
Nothing blocked. This fixture company's history is genuinely empty, so the read lands with no points, and the trend still says No data for this range. That is the true claim for a read that landed. Only a failed read changes the wording.
Asserted in the captured DOM — No data for this range · Try a different date range
Residual seen in the capture
Under the failed state, the stats strip beneath the chart still reads "No data points in range." That strip is MetricInsight's footer, not the trend body. It is reported to the driver as a follow-up rather than widened into this PR.