Forum Discussion
Embedded Visuals - "This content isn't avaliable" Error
Hi cchilton
Since the issue occurs after the application has been idle for some time, this strongly indicates that the embed token is expiring during inactivity and is not being refreshed proactively. When the user interacts again (such as rearranging tiles), the visuals attempt to reload using an expired token, which results in the “This content isn’t available” error.
To address this we recommend working with your backend team to:
- Ensure embed tokens are refreshed proactively (for example, every 45–50 minutes) rather than only on initial load or after failure.
- Verify that a fresh token is generated on each refresh request and not reused.
- Confirm that all embedded tiles are consistently using the updated token.
If the issue continues after implementing the above, I would recommend raising a Microsoft Fabric Support and Status | Microsoft Fabric so the team can perform deeper backend analysis to identify the root cause.
Hi! We made the changes you suggested. We are still facing the issue. For context I noticed this issue happens when we leave the application sitting open for awhile. Maybe one or two hours at most and then when we rearrange a tile we get the "This content isn't availiabe error." Do you have any other advice I can relay to our backend team?
Hi cchilton
Since the issue occurs after the application has been idle for some time, this strongly indicates that the embed token is expiring during inactivity and is not being refreshed proactively. When the user interacts again (such as rearranging tiles), the visuals attempt to reload using an expired token, which results in the “This content isn’t available” error.
To address this we recommend working with your backend team to:
- Ensure embed tokens are refreshed proactively (for example, every 45–50 minutes) rather than only on initial load or after failure.
- Verify that a fresh token is generated on each refresh request and not reused.
- Confirm that all embedded tiles are consistently using the updated token.
If the issue continues after implementing the above, I would recommend raising a Microsoft Fabric Support and Status | Microsoft Fabric so the team can perform deeper backend analysis to identify the root cause.