Everything I could decide myself is decided. What's left needs
you. Each one carries the recommendation of the session that raised it — if you
agree, pick it and press Done. A model's opinion, where there is one, appears on the card
as a receipt line; cards with no receipt were never put to a model. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
1wo_enrichment (AppFolio work-order enrichment sweep) has been red every day since 2026-09-15: it hit its full ~640s Lambda drain budget today and only got through 63 of 83 eligible properties (216 WOs enriched, 708 stranded unreached). Portfolio size grew from ~8 to 83 properties between 09-11 and 09-24. A per-org weekly-cadence lever already exists (scripts/set-wo-enrichment-cadence.ts, decision b89464070/PR #9847) but isn't applied broadly enough to relieve the daily run. This is a capacity ceiling, not a code defect - the job is at its architectural limit (900s AWS Lambda max).
In plain terms. Your daily work-order refresh job can no longer keep up with how many properties you now have — should we run it more than once a day, or slow it down for properties that aren't live yet?
The session raising this recommends: Move non-live properties to weekly refresh the lever already exists and ships today with a config change, not new engineering, and slower refresh on units nobody is renting yet has the smallest customer impact Tried first, unsuccessfully: Investigated the code path (planWoEnrichmentSweep / sweepWoEnrichmentAcrossProperties), pulled real Sentry event history (10 straight failing days) and today's actual CloudWatch log line (properties=157 results=83 durationMs=640058 — proves the run used its full time budget), and checked for an existing open decision on this exact job (none found; the one related block, b89506754, is a different, already-resolved job).