Forum Discussion
Solution SageReal time dashboard
Hi powerbidev123 ,
I believe this behaviour is connected to the newer Live refresh implementation that became generally available in June 2026.
Live refresh now works by periodically checking the ingestion high-water mark for each supported visual. When new data is detected, the visual query is triggered. The Refresh rate limit controls the minimum time allowed between those refreshes, while the Fallback refresh interval controls visuals that do not support ingestion detection.
You can check the current configuration under:
Manage → Refresh settings → Live refresh → Settings
From there, confirm the values configured for:
- Refresh rate limit
- Fallback refresh interval
The current documentation does not describe another setting that restores the older Continuous-refresh mode or allows a refresh interval below the minimum shown in the interface. The older option appears to have been replaced by this Live refresh model. Microsoft lists Real-Time Dashboard Live Refresh as generally available from June 2026.
I also found an earlier community thread reporting the same change from Continuous refresh to a minimum 10-second rate. After the refresh settings were checked and the behaviour remained unchanged, Microsoft Community Support recommended opening a Fabric support ticket so that the tenant and capacity-specific behaviour could be investigated.
Based on that, I would:
- Confirm the Live refresh settings above.
- Test whether the visual supports ingestion detection by checking its last-refresh details.
- If 10 seconds remains the lowest available rate and this affects your operational use case, raise a Fabric support ticket and include the workspace, dashboard, capacity region, screenshots and the refresh behaviour you observed before and after the update.
From the currently published documentation, I do not see a supported way to force these visuals to refresh faster than the minimum exposed in the new Live refresh settings.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
Resident RockstarHi powerbidev123 ,
I believe this behaviour is connected to the newer Live refresh implementation that became generally available in June 2026.
Live refresh now works by periodically checking the ingestion high-water mark for each supported visual. When new data is detected, the visual query is triggered. The Refresh rate limit controls the minimum time allowed between those refreshes, while the Fallback refresh interval controls visuals that do not support ingestion detection.
You can check the current configuration under:
Manage → Refresh settings → Live refresh → Settings
From there, confirm the values configured for:
- Refresh rate limit
- Fallback refresh interval
The current documentation does not describe another setting that restores the older Continuous-refresh mode or allows a refresh interval below the minimum shown in the interface. The older option appears to have been replaced by this Live refresh model. Microsoft lists Real-Time Dashboard Live Refresh as generally available from June 2026.
I also found an earlier community thread reporting the same change from Continuous refresh to a minimum 10-second rate. After the refresh settings were checked and the behaviour remained unchanged, Microsoft Community Support recommended opening a Fabric support ticket so that the tenant and capacity-specific behaviour could be investigated.
Based on that, I would:
- Confirm the Live refresh settings above.
- Test whether the visual supports ingestion detection by checking its last-refresh details.
- If 10 seconds remains the lowest available rate and this affects your operational use case, raise a Fabric support ticket and include the workspace, dashboard, capacity region, screenshots and the refresh behaviour you observed before and after the update.
From the currently published documentation, I do not see a supported way to force these visuals to refresh faster than the minimum exposed in the new Live refresh settings.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.