Forum Discussion
embedded-expiration/timeout issue?
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.
- ThomasDay10 years agoImpactful Individual
wabreza Here are the tech details of the error. Let me know what you see as a root cause.....and thanks, Tom
- wabreza10 years agoMicrosoft Employee
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?
- ThomasDay10 years agoImpactful Individual
wabreza No the token timeout is set to 1hr. We've had 403's forever to be honest. They happen when the site has been sitting and I click on another tab in a report. Time is 3-7 minutes, but not always. Sometimes longer...but seldom a non-issue. We have 4 embedded reports up behind our paywall. The tabbed ones are the main issue. There are lots of filters and data...and the app is really useful and fast. Very good market reception. Can't say I recall a non-tabbed one giving me trouble but I'll look more carefully going forward. Now that we're live and have users starting up...we're paying more attention in general. Tom