Known Issue: Deposit-Protection Overdue Alerts Don't Surface in the Work Queue Until the Next Morning
Known Issue: Deposit-Protection Overdue Alerts Don't Surface in the Work Queue Until the Next Morning
Status: Known issue identified in v0.1.287. Fix is in progress. This article explains the current behaviour, the impact, and the expected resolution.
Summary
When a tenancy's 30-day deposit protection deadline passes, the tenancy card on the Tenancies list correctly highlights with an overdue border colour. However, this same overdue status is not immediately reflected in the Work Queue. The Work Queue only picks up the alert after the nightly compliance sweep runs — meaning there can be up to a 24-hour delay before an actionable Work Queue item appears.
How the 30-Day Deposit Deadline Works Today
Under the Tenancy Deposit Protection rules, a landlord or agent must register a deposit with a government-approved scheme within 30 days of receiving it.
The platform tracks this in two places:
1. Tenancy Card (client-side)
In the Tenancies list, each card computes:
depositDeadline = tenancy.startDate + 30 days
depositOverdue = today > depositDeadline AND depositScheme == null/none
This calculation happens in the browser. If depositOverdue is true, the card border changes colour to signal a problem. This indicator is real-time and accurate.
2. Work Queue (server-side, nightly)
The Work Queue router queries the compliance_checks table to build its list of compliance alerts. This table is populated by a nightly background sweep.
Because the Work Queue does not run its own live query for unprotected deposits, a tenancy that crosses the 30-day threshold during the day will not appear in the Work Queue until the sweep runs overnight.
What This Means in Practice
| Scenario | Card border colour | Work Queue alert |
|---|---|---|
| Deposit protected, within 30 days | Normal | No alert |
| Deposit unprotected, within 30 days | Warning indicator | No alert |
| Deposit unprotected, past 30 days (same day) | ⚠️ Overdue indicator | ❌ Not yet shown |
| Deposit unprotected, past 30 days (next day after sweep) | ⚠️ Overdue indicator | ✅ Shown in Compliance Alerts |
The practical risk is that an agent or landlord reviewing the Work Queue on the day a deadline is missed will see no urgent action item, even though the statutory deadline has already passed.
Planned Fix
The workQueue procedure in the dashboard router will be updated to include a live sub-query — independent of the nightly sweep — that fetches all tenancies matching:
status = activedepositSchemeisnullor'none'startDate < (today − 30 days)
This will power a new Deposit Protection Overdue section in the Work Queue, displayed above the existing Compliance Alerts section, so the most time-critical items are always visible at the top.
Once this fix is released:
- Overdue deposit protection alerts will surface in the Work Queue the same day the deadline is missed.
- No dependency on the nightly compliance sweep for this specific alert type.
- The nightly sweep will continue to update the
compliance_checkstable for all other compliance checks.
Workaround
Until the fix is released, you can identify overdue deposit protection cases by:
- Navigating to Tenancies in the dashboard.
- Looking for tenancy cards with an overdue border highlight — this indicator updates in real time.
- Checking the tenancy detail to confirm the deposit scheme status and start date.
Do not rely solely on the Work Queue for deposit protection compliance monitoring until the fix is confirmed live.
Affected Versions
| Version | Status |
|---|---|
| v0.1.287 and earlier | ⚠️ Affected |
| Fix release (TBD) | ✅ Resolved |
Related
- Changelog — v0.1.287
- Work Queue documentation
- Compliance Alerts overview