Hi there! If you're noticing that the Dashboard takes longer to load during busy mornings or right after your team clocks in, you're not alone. Happy to help explain what's happening and how to improve things.
Summary
Dashboard widgets timeout or load slowly when concurrent users exceed 500.
Symptoms
- Dashboard page takes 10–30 seconds to fully render
- Individual widgets show spinning loaders or "Unable to load data" messages
- Issue occurs consistently between 7:00–9:00 AM and 4:00–6:00 PM local time
- Refreshing the page occasionally helps, but not consistently
Affected Environments
- Web app (all browsers)
- Particularly noticeable for users with 10+ dashboard widgets configured
- Organizations with 50+ active technicians
Cause
During peak usage windows, the real-time aggregation queries that power dashboard widgets compete for database connection pool resources. When concurrent requests exceed our current capacity threshold, some queries queue rather than execute immediately, resulting in the delays you're seeing.
Immediate Resolution Steps
Here are a few things you can try right now:
- Reduce widget count: Click Edit Dashboard and remove widgets you don't check daily. Each widget makes a separate query.
- Adjust date ranges: Widgets set to "Last 30 Days" or "This Quarter" require heavier aggregation. Try "Today" or "This Week" during peak hours.
- Stagger team login times: If possible, have dispatchers or supervisors log in 15 minutes before or after the main technician rush.
- Clear browser cache: Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) to hard-refresh if you see stale data.
Longer-Term Improvements
Our engineering team has identified this as a priority. We're implementing:
- Query result caching for dashboard widgets (rolling out in 3.3.2)
- Connection pool scaling during known peak windows
- Optional "Light Dashboard" mode with pre-aggregated snapshots
Status
Fix targeted for release 3.3.2 (mid-April). I'll update this article once the release is live.
If you're seeing slowness outside of peak hours or these steps don't help, please reach out to Support with your account ID and the specific times you experienced issues. We can check if there's something else going on.