Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
1
In plain terms. Situs's work-order refresh can't keep up because about 7,500 old repair orders (some from 2021) still look open on our side — should we close out the ones AppFolio says are finished, or have the nightly refresh skip anything older than a set age?
The full question, as raised
wo_enrichment red daily since 10-16: 35/36 stranded properties are Situs (org_a3376147); 7,497 unreached, maxStaleness rising 48h→168h, ~250 enrichments/day serial vs ~3,900/day needed for the 48h bar. Sample [propflow-prod] situs property-41: 1,407 of 1,484 WO rows status=dispatched, 1,079 created 2021-2023, pmsStatus null on all — onboarding import left historic WOs open; the 1-min mirror only refreshes a ~90-day CreatedAt window. Options: one-time reconcile of Situs WO statuses against AppFolio (large prod backfill, needs direct approval), or an age cutoff in the sweep queue.
Why, and what was tried
The session raising this recommends: Close out finished ones Fixes the wrong 'open' status PMs see, not just the alarm; an age cutoff would hide the same stale rows Tried first, unsuccessfully: Read 6 days of prod run rows (all red, same 36 properties, staleness rising), mapped stranded properties to orgs, profiled one Situs property's WOs, checked prior fixes (terminal-skip #16420 only skips 12 because our rows carry no PMS status) and the resolved weekly-cadence decision b90242176 (weekly would cut capacity further).