Hello fellow Embedders, I have a site that is working great...until it sits for 3 minutes or perhaps 5. Then I get this when I click another tab in the report.The token expiration is set for 1 hr, btw, so I'm not sure what's up. A refresh sets things straight. What's to be done here..any ideas?Thanks,Tom

arujindal Actually I never got an answer from the forum. I did get to the Microsoft person who built the github code for embedding V1. (You'll notice this is quite an old post). The end of this story was that there is a php command in the embedding code we used that sets the timeout period and it's measured in seconds not minutes, so turns out se had set the timeout to 60 instead of 3600 for a one hour timeout period. I really don't know how the sharepoint embedding works, but that's what did it for us. Hope that helps,Tom

If you click on one of the "See Details" links do you get an activity or request id GUID? If so please share. I'll be able to look up the root cause of the issue with this information.

If this does come down to being a timeout issue you can try one of the following: In a server generated app you can get around this by generating a token for each render of the page.In a single page app (SPA) - one option is to set a client-side timer on your page/view that is shorter than your token expiration. At that point you can regenerate the token and reload the report passing in the new access token.

wabreza Here are the tech details of the error. Let me know what you see as a root cause.....and thanks, Tom

Its a 403 which is an access issue. What is the expiration of your generated tokens? Is the expiration you are setting inline which the timeout you are seeing in the embedded report?

embedded-expiration/timeout issue? | Microsoft Fabric Community

18 Replies

wabreza
Microsoft Employee
10 years ago
If you click on one of the "See Details" links do you get an activity or request id GUID? If so please share. I'll be able to look up the root cause of the issue with this information.
wabreza
Microsoft Employee
10 years ago
If this does come down to being a timeout issue you can try one of the following:

In a server generated app you can get around this by generating a token for each render of the page.
In a single page app (SPA) - one option is to set a client-side timer on your page/view that is shorter than your token expiration. At that point you can regenerate the token and reload the report passing in the new access token.
- ThomasDay
  Impactful Individual
  10 years ago
  wabreza Here are the tech details of the error. Let me know what you see as a root cause.....and thanks, Tom
  - wabreza
    Microsoft Employee
    10 years ago
    Its a 403 which is an access issue. What is the expiration of your generated tokens? Is the expiration you are setting inline which the timeout you are seeing in the embedded report?

Forum Discussion

embedded-expiration/timeout issue?

18 Replies

Related content

Averagex issue

Relationship Issue

SUMMARISECOLUMNS ISSUE

Refresh issue

RLS issue.