p11-x-combine-companies — refusal, not outage
24 Sept 2026 · branch fix/two-company-refusal-review-held-flags · captured against propflow-stage · at 14f9d7aaaa
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.
Fixture Property Co plus Fairhaven Residential (TEST) ticked in the company switcher, then Done. Every feed on this page refuses a two-company pick by name. The page shows one notice naming both companies and the lists held back; no could not be loaded banners, no Try again.
Asserted in the captured DOM — The review queue answers for one organization at a time. · Fixture Property Co · Fairhaven Residential (TEST) · Not shown until you pick one · Held emails answers for one organization at a time.. The by-name notice and the held-back lists are on screen.
The same pick. The grading feed behind the Needs a look chip refuses it by name. The chip is dropped rather than showing an invented 0, and the notice names both companies.
Asserted in the captured DOM — Conversation grading answers for one organization at a time.. The grading refusal is named.
Stage data (anonymized), smoke user (staff), branch dev server. Capturing this found two more instances of the same stale-after-switch shape, both fixed in this PR: the grading flags and the held-emails feed were keyed only on the building filter, which reads All before and after a company switch, so they never re-read. Both now re-read on the selection, each pinned by a test that fails without it. Separate, NOT in this PR: the conversations LIST itself still shows its refusal as a red error toast over No conversations found. (visible above); that is the list route's refusal, left to the combine-companies builds.