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 cchilton
Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further.
We reviewed our token refresh lifecycle and this is how it works.
- The stored token is fetched from the database
- The system calculates how long ago the token was created
- Then it checks if the token age exceeds the configured threshold (50 minutes) a new token is generated. Otherwise, the existing token is used.
When the user moves a chart around the visual refreshes and sometimes we receive the above error message. Given the additional information I have provided, do you have any other advice on how we can modify our token handling process to prevent this error message from appearing?
Hi cchilton
Based on your token lifecycle, the issue is likely due to the token expiring during the visual refresh rather than before it starts. Currently, you are validating the token based on how long ago it was created (50-minute threshold). However, in embedded scenarios a token must remain valid for the entire duration of the render operation. When a user moves a chart, Power BI triggers multiple backend requests, and if the token is close to expiry, it may expire in the middle request. This can result in intermittent failures like “This content is not available.”
Recommended approach :
- Check the actual token expiry time instead of creation time
- Add a buffer (e.g., refresh if less than 5–10 minutes remaining)
These changes ensure the token remains valid throughout the entire rendering process and should prevent the intermittent failures.
Hope this helps !!
Thank You.
Hi cchilton
We wanted to follow up to check if you’ve had an opportunity to review the previous responses. If you require further assistance, please don’t hesitate to let us know.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?