In my experience, this particular behavior tends to surface when dispatch teams are working with high-volume boards and using multiple filter combinations. What I typically recommend is understanding the underlying cause before attempting any of the resolution steps, since the fix is straightforward once you recognize what's happening.
Summary
Jobs temporarily vanish from the dispatch board after refreshing the page due to aggressive client-side filtering that can miscalculate visibility states when combined with certain filter presets.
Symptoms
- Jobs visible before refresh are no longer displayed after pressing F5 or using the browser refresh button
- The job count indicator at the top of the board shows fewer jobs than expected
- Searching for a specific job ID by typing in the search bar still returns the missing job
- Other dispatchers viewing the same board may see the jobs normally
- Issue resolves temporarily after clearing browser cache or using incognito mode
Affected Versions
FieldPulse web application versions 3.0.4 through 3.2.0, primarily affecting Chrome and Edge browsers. Less commonly observed in Firefox.
Cause
The dispatch board uses client-side caching to improve load performance. When a user has active filters applied (particularly date range filters that cross midnight UTC boundaries or technician filters with large teams), the cached filter state can become desynchronized from the server response during refresh. In my experience, this happens most frequently when dispatchers leave the board open overnight and return to refresh the next morning.
What I typically recommend is reviewing your team's workflow around filter usage, as the root cause relates to how filter parameters are serialized in the URL hash and then reconstructed on page load.
Resolution
Immediate fix:
- Click the Clear Filters button in the top-right corner of the dispatch board (this resets the client-side filter state)
- Wait for the board to reload with all jobs visible
- Reapply your desired filters one at a time
- Avoid using the browser's back button to restore filter combinations
Preventive configuration:
- Navigate to Settings > Dispatch > Board Preferences
- Enable Disable filter persistence on refresh — this prevents the cached state from persisting
- Alternatively, bookmark specific filter combinations using the Save View feature rather than relying on browser history
For administrators:
In my experience, teams that establish a habit of using saved views rather than manual filter combinations see significantly fewer instances of this issue. What I typically recommend is training dispatchers to treat the clear filters button as a first troubleshooting step whenever the board appears incomplete.
Workaround
If the issue persists and you need immediate visibility: open the dispatch board in a second browser tab without any URL parameters (just /dispatch), then manually apply filters. This bypasses the serialized filter state entirely.
Status
Engineering has identified the root cause in the filter state hydration logic. A fix is targeted for release 3.3.0, which improves how filter parameters are validated against the current session context on page load.
For additional context on how the dispatch board manages data visibility, see How do you prevent dispatchers from becoming a bottleneck? in our community discussions.
