Summary: Hard browser refresh restores missing jobs when client-side filtering causes display issues.
We've been running into this one pretty regularly in our ops, and while it's not a permanent fix, it's saved us from a lot of unnecessary panic. Here's what we're doing when jobs vanish from the dispatch board.
Symptoms
- Jobs you know exist aren't showing on the dispatch board
- Refreshing the page with F5 doesn't bring them back
- The job count badge shows a different number than visible cards
- Filter pills appear empty or show "0 selected" when they shouldn't
Cause
The dispatch board uses aggressive client-side caching to stay snappy. Occasionally the filter state gets desynced from what's actually in the DOM — usually after rapid filter changes or if you leave the tab open overnight. The data's there, the view just won't show it.
Resolution
Normal refresh won't cut it. You need a hard refresh to dump the cached state:
Windows: Ctrl + Shift + R or Ctrl + F5
Mac: Cmd + Shift + R or hold Shift and click the reload button
You'll know it worked if the board shows a brief loading spinner and your filters reset to default.
The Actual Workaround
Since hard refresh clears your filters, here's how we handle it without losing our place:
- Note your current filters — screenshot if needed, or just remember the tech/date range
- Hard refresh the page
- Reapply filters one by one — don't rush, give each one a second to settle
- Check the count badge before moving to the next filter
Pro tip: We keep a saved filter set called "Today's Active" that we can reapply in two clicks. If you're not using saved filters yet, you're making this harder than it needs to be. Also worth mentioning: pinning the dispatch board tab and never closing it seems to make this worse — we've started doing a hard refresh first thing every morning as preventative maintenance.
When This Isn't the Fix
If jobs are still missing after hard refresh, check ts-016 — Jobs Disappearing from Dispatch Board After Refresh. That's a different issue where the jobs actually aren't loading from the server.
Status
Engineering is aware and working on filter state persistence in 3.4. No ETA yet, but this workaround has been solid for us in the meantime.