- Shipped
- July 2, 2026 at 4:30 PM UTC
- Author
- Kamo
- Commit
- 2b594d0
findApplicableAllotments filtered 'AND la.isActive = true', so getMostSpecificAllotment returned a less-specific ACTIVE fallback (or nothing) when a member's specific allotment was suspended — the suspension was invisible to every suspension-aware caller (the Leads-Available alert, the per-market grid, and the accept flow), so suspending a member never cleared their lead alert. Drop the isActive filter; callers already check isActive. Also move the SUSPENDED check in acceptNextLead out of the if(!ffa) block so an explicit suspension blocks free-for-all acceptance too (FFA only bypasses the credit balance/spend checks, not a manager's suspension).