Monitoring, data storage, and browser refresh are separate steps. A check can finish correctly before its newest result appears on the page you are viewing.
Customer dashboard refresh timing
The dashboard requests an updated account snapshot approximately every 60 seconds while the page is visible and the browser is online.
It also requests an update promptly when:
- You return to a previously hidden dashboard tab.
- The browser reconnects after being offline.
- Another open dashboard tab writes a newer authenticated snapshot to shared browser storage.
Multiple dashboard tabs coordinate polling so they do not all send the same recurring request. Temporary failures use increasing retry delays, up to about five minutes, and keep the existing cards visible.
Why cached data appears first
The dashboard can render a private browser-cached snapshot while it requests current data. This avoids a blank screen and does not expose one user's data to another account.
The browser cache:
- Is separated by the signed-in account identity.
- Uses a schema version so incompatible old data is ignored.
- Is discarded after 15 minutes.
- Is replaced when a newer authenticated dashboard response arrives.
The Last update indicator describes the age of the monitoring data represented by the loaded snapshot. It receives a warning style after 10 minutes.
Cached display does not pause monitoring. Checks continue through the scheduler and workers whether or not the dashboard is open.
Monitor Details refresh timing
Monitor Details loads its selected summary when the page opens and when you choose a different range. A loaded monitor-and-range result is kept in memory for one minute so switching back quickly does not repeat the same database work.
Saving monitor settings, pausing or activating the monitor, and other state-changing actions clear the summary cache and request a fresh result.
Unlike the main dashboard, the Monitor Details charts are not intended to poll continuously while you leave the page open. Reopen the page or change the range after a new check when you need an immediate updated chart.
Check interval is not refresh interval
A one-minute monitor is scheduled more frequently than a five-minute monitor, but that does not mean every screen redraws once per minute. Before a result appears, the service may need to:
- Select the due monitor.
- Process the queued request.
- Wait for the request timeout when the endpoint is unresponsive.
- Run regional confirmation for a possible outage.
- Save the check, rollup, and any state change.
- Serve the next page or dashboard request.
This processing time is most noticeable for timeouts and region-confirmed failures.
Determine whether monitoring or display is delayed
- Check the dashboard's Last update indicator.
- Open Monitor Details and review Last checked.
- Open Detailed Logs and look at the newest row.
- Confirm that the monitor is Active.
- Compare the newest log time with the configured interval.
If Detailed Logs contain the new check but the dashboard card is older, monitoring worked and the display is waiting for refresh. If the logs are also missing several expected results, investigate scheduling or processing.
Protect your session and cached data
Use a private device for account access and sign out on shared computers. Browser storage is an authenticated loading optimization, not a public status feed. Clearing site data removes the local snapshot and session information but does not delete monitors or server-side history.