- Shipped
- September 27, 2026 at 4:23 PM UTC
- Author
- Kamo
- Commit
- f1fce70
useOrgChanges coalesces a burst and hands onChange only its last frame, so testing isApprovalChange on that frame lost an APPROVAL followed within 400 ms by the run's RUN_FINISHED or a STATE change: the Interaction Center pane and the Workforce list (which do not poll) never showed the new request. useOrgChanges gains an optional per-frame filter applied before coalescing (a refused frame neither restarts the wait nor replaces the delivered one; the reconnect null always passes); the approvals pane, badge and list pass isApprovalChange as that filter.