UI Cache Invalidation / Forced Dashboard Updates
R
Ran Nir
When changes are made to dashboards, widgets, scorecards, or other UI elements in Port, end users do not automatically receive the updated view.
Currently:
- A hard refresh (or clearing browser history/cache) is required to see new changes.
- A soft refresh is sometimes insufficient
Proposed Solution (from @galtomer)
A config/version check or ETag-based mechanism that busts the locally cached view whenever a dashboard, widget, or scorecard is changed on the backend. This would ensure users automatically receive the latest UI state without manual intervention.