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.
1pickWorkOrderForVendorReply (reply-attribution.ts:411-412) keeps only handymanNotifiedAt-stamped WOs, so a self-reported (unpaged) WO loses to stale WILL-002174 (turnover, 2026-07-31, dispatched, never synced to AppFolio) on appfolio-45; sweepHandymanOpenLeftovers excludes turnoverId WOs. Fix the picker + preclean and cancel WILL-002174, or cancel WILL-002174 only?
In plain terms. An old test job from July is still open at the test building, and every night the handyman's texts about the new job get pinned to that old job instead, so three eval checks fail. Should I close the old job AND fix the rule so a tech's own new report isn't skipped for an older job, or only close the old job?
Why, and what was tried
The session raising this recommends: Close the old job and fix the rule The skip is a real routing bug for any in-house tech who reports a job himself; closing the job alone hides it until the next stale one. Tried first, unsuccessfully: Read tonight's worker log (3 refusals all on WILL-002174), the 10-20..10-27 log history (it catches his texts every night since 10-22), the picker code and the pre-clean filter; did not write to production from an unattended alert run.