Work order page — a failed update to the property system is visible
the manager's progress card says when an update did not go through, and says nothing when it did
3 Oct 2026 · branch p9-situs-wo-sync-visibility · captured against propflow-stage · at 5b6c2fad6cb+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 last update landed nothing
A dispatched work order on the stage sandbox building, set for this capture to the exact state the work-order pipeline writes when a write to the property system landed nothing (tried three times). Under the progress rail the card now reads Couldn't update your property system, in the red the brand keeps for something blocked, with one short line telling the manager to check it there.
What it does not say: any error text, the vendor's name, how many times it was tried, or that it will retry. A write that landed nothing is not guaranteed another try, so promising one would be a made-up fact.
Asserted in the captured DOM — Work order progress · Couldn't update your property system · Check it there.. The notice title and its body are in the captured DOM.
Sections 2–3 and notes
2 · Part of an update failed and is queued to go again
A second sandbox work order, set to the state the pipeline writes when part of a write failed and the failed pieces are queued for the next try. The card says Couldn't update your property system yet and that the changes will be sent again, in amber: nothing is needed from the manager yet.
The same status also marks a perfectly healthy "new change waiting to go out" moment, for example right after an approval. The card tells the two apart by whether a write has actually failed since the last success, so a normal approval never shows this.
Asserted in the captured DOM — Work order progress · Couldn't update your property system yet · They'll be sent again.. The retry notice title and body are in the captured DOM.
3 · A healthy work order looks exactly as before
A work order on the same building with nothing recorded about its updates to the property system. No notice under the rail: nothing is shown unless the row says a write failed, and the card never claims "up to date" on its own.
Asserted in the captured DOM — Work order progress. The card rendered; the absence of the notice is shown in the picture and pinned by the unit test.
What the captures checked
The two failure states were stamped onto two stage sandbox work orders (test company, synthetic data) for the capture, with the same two fields the pipeline writes, and removed again right after. Before this change all three pages showed only the rail.