Forum Discussion

ThomasDay's avatar
ThomasDay
Impactful Individual
10 years ago

embedded-expiration/timeout issue?

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 f...
ThomasDay's avatar
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's avatar
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?

  • ThomasDay's avatar
    ThomasDay
    Impactful Individual
    10 years ago

    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

    • wabreza's avatar
      wabreza
      Microsoft Employee
      10 years ago

      You mentioned you have 4 embedded reports.  Are they all embedded within the app at the same time?  Or are they embedded seperatly in different views?

       

      If they are all embedded in the page at the same time I'm thinking of some potential issues where their may be some shared state (cookies/local storage) that have the potential to be shared accross the iframes.

      • ThomasDay's avatar
        ThomasDay
        Impactful Individual
        10 years ago

        wabrezaThey all are called via the same iFrame.  We have a wordpress site where the page behind our paywall has a side menu navbar where you pick the report--and it's retrieved via it's id from the collection/workspace.  There is seldom an issue as it's retrieved...just when it's been sitting and I click a report page tab or sometimes just click a slicer on the idle page and sometimes there are no problems.  

         

        • This morning's picture of problems had a single chrome tab open to our site iframe and the x's appeared when I clicked a powerbi report tab to switch pages.
        • The picture I sent to this topic, had two chrome tabs open to our site--and the second chrome tab iframe presented problems when I clicked a powerbi report tab to switch pages.
        • BTW, the first chrome tab iframe has not shown problems at all and has been sitting for quite some time. 

        Is there something I can do to understand any shared state issues?

        Tom