Work-order Pipeline — the two bulk buttons ask first
Flush all now opens a confirmation before anything goes to AppFolio; Kill all's count matches what the server deletes.
23 Sept 2026 · branch detached · captured against propflow-stage · at ba8620110c
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 · 1 · The page, unchanged at rest
The header keeps both buttons exactly where they were. Nothing about the resting page changed.
Asserted in the captured DOM — Pipeline · Sync queue
2 · 2 · Flush all opens a confirmation
Before this change the first click posted to flush-all and pushed every waiting work order, for every company, into AppFolio. Now the click opens the same in-page dialog Kill all uses. It states the count and that the work orders go into AppFolio for every company, and nothing is sent until a staff member presses Send to AppFolio.
Asserted in the captured DOM — to AppFolio? · for every company · Send to AppFolio · Cancel
3 · 3 · Kill all counts only what it deletes
The title counts only waiting rows that never reached AppFolio, which are the rows the kill-all route deletes. Rows that already exist in AppFolio are named as skipped, not counted.
Asserted in the captured DOM — Delete · never made it to AppFolio · Delete all
