Forum Discussion
Power BI Embedded Report Change Detection Timeout
I have built a very simple test report in power BI that has changed detection enabled and is set to check every 10 seconds, this report has been embedded in a Power App. Initially everything works fine but after a certain amount of time the change detection seems to fail or timeout with error:
We had trouble loading the settings for change detection, so this page won't refresh automatically. Try again in a few minutes.
Please try again later or contact support. If you contact support, please provide these details.
Activity ID: bbd8e402-7feb-40a0-9663-9368b7ab0c99
Request ID: 7fc9ecb3-0106-44c2-b049-4536c207dcd1
Correlation ID: a4d5144d-b480-5038-0970-2c860df2ab7d
Status code: 401
Time: Thu Aug 27 2026 07:34:52 GMT+0200 (South Africa Standard Time)
Service version: 13.0.28513.279
Client version: 2608.3.30685-train
Cluster URI: https://WABI-NORTH-EUROPE-H-PRIMARY-redirect.analysis.windows.net
Hi,
The 401 after "a certain amount of time" is your embed token expiring. Change detection keeps polling every 10 seconds, but once the token passes its lifetime the service rejects the calls, and you get exactly this "couldn't load change detection settings" 401. It works initially and fails later because it's tied to the token clock, not the report.
The fix is token renewal: refresh the embed token before it expires and re-apply it to the embedded report, rather than letting the original one run out. In a Power Apps embed you have limited control over that, so it's worth checking whether the Power BI tile/component you're using handles token refresh at all, since some don't, and that's usually the real ceiling on long-running auto-refresh scenarios.
Paco
Helping data analytics leaders distribute their reports
6 Replies
- SamInogic
Super User
Hi,
The 401 error usually points to an authentication/session issue, rather than a problem with the change detection itself.
Since it works initially and then stops after some time, I would suggest checking whether the Power BI authentication token/session is expiring or being lost inside the Power App.
Also, try changing the change detection interval from 10 seconds to 30–60 seconds and test again. If the issue still occurs, check the Power BI/Power Apps embedding and authentication setup.
If it continues, the Activity ID, Request ID, and Correlation ID from the error can be shared with Microsoft Support for further investigation.
Hope this Helps!!
Thanks!
Hi SamInogic,
Thanks for the response, let me try this out and see how it goes.Appreciate the help!
- DataTako
Resolver IV
Hi,
The 401 after "a certain amount of time" is your embed token expiring. Change detection keeps polling every 10 seconds, but once the token passes its lifetime the service rejects the calls, and you get exactly this "couldn't load change detection settings" 401. It works initially and fails later because it's tied to the token clock, not the report.
The fix is token renewal: refresh the embed token before it expires and re-apply it to the embedded report, rather than letting the original one run out. In a Power Apps embed you have limited control over that, so it's worth checking whether the Power BI tile/component you're using handles token refresh at all, since some don't, and that's usually the real ceiling on long-running auto-refresh scenarios.
Paco
Helping data analytics leaders distribute their reportsHi Paco,
Appreciate the response, I was monitoring the Dashboard just opened in a tab in my browser with my dev tools open and it definitely seems to be the embed token.
Not sure what I can do about it in Power Apps though, but let me have a look.
Thanks!
v-achippaCommunity Support
Hi WillemNieu,
Thank you for reaching out to Microsoft Fabric Community.
Thank you SamInogic for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution response by the user for the issue worked? or have you raised a support ticket?
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thanks and regards,
Anjan Kumar ChippaHi Anjan,
DataTako's reponse correctly pointed out the issue, as for a solution to the embed token expiring, I don't have a solution yet, pehaps you can assist me with raising a ticket?Kind regards,
Willem
