Objective
- Fix incorrect “0 inspections scheduled” (or equivalent gap) on the Scheduled Jobs dashboard visualization for affected tenants (example: AJF on Wed 5/6) while other brands show correct counts.
Background
- A single-instance anomaly suggests date-boundary, timezone, aggregation, or data-partition logic rather than universal UI failure.
- UI entry points include
attik-frontend/src/components/dashboard/Scheduled/DashContainer.tsxandScheduledJobsDropMenu.tsx; related volume copy also appears inInternalVsOnlineSplit.tsx.
Scope
Frontend
- Trace how scheduled counts are computed and bucketed by day for the dashboard widgets above.
Backend
- Any API feeding scheduled job counts (search dashboard-related routes in
attik-backend/src/routes/)—Decision needed after reproducing with AJF data for the specific date range.
References
attik-frontend/src/components/dashboard/Scheduled/DashContainer.tsxattik-frontend/src/components/dashboard/Scheduled/ScheduledJobsDropMenu.tsx
Original description
AJF instance shows a random gap on Wednesday 5/6 indicating 0 inspections were scheduled, but that is not correct. No other brand appears to be having the same issue.
Additional example
In TLC, the dashboard data for Scheduled Jobs appears to be shifted by one day. Jobs shown for 5/17 were actually scheduled on 5/18 by the team.
