Question
When I try to open my shared dashboard, I get an error message saying Authentication expired, please reload your dashboard. What does it mean?
Answer
The error message means that you don't have the proper access to any of the dashboards that you want to view. To solve this, a user with the Admin role in Explore must go to Explore > Admin> Editor Authorizations and change your access to at least Can view for any of the dashboards that you want to view.
For more information about sharing dashboards, see the article: Sharing dashboards.
8 Comments
I'm having the same error message, but checking in Support, I am an admin for explore (and the only seat we actually have in Zendesk). When I try to follow the instructions given above to see the editor authorizations page, I see this
Which takes me to a Support article. There's no way around it that I can see.
This is the error I'm seeing:
Thank you in advance!
Fiona
We're having the same issue. I also have an Admin role and when I click Explore > Admin> I get sent right to Schedules. I tried to edit the url to get straight to Admin, thinking this was maybe a link issue, but I again get sent to Schedules.
I think that's because you have 'editor' role in Explore. I just changed mine to editor, from admin, and checked and I see that email delivery icon only too. When I added myself back as 'admin', I saw the three icons like in my previous screenshot.
I just tried again today and I'm not getting the error message anymore!
I also get the error message "Authentication expired, reload your dashboard 1." when in the edit-mode of the dashboard. I am an account administrator (the account owner, even), so why does this happen?
Hello Hege Farsund Solheim
Are you also an Admin of Explore? When in Support, if you open your profile page, on the left-hand side, under Explore, which role do you have?
Hi, I received this error when creating a new query and choosing row attributes, a dashboard was not involved at all. Any ideas why? This is not the first query I have done.
Hi Tina -
If your permissions are set correctly (as described above) and you're still seeing this error, it sounds like you may have found a bug, in which case I suggest opening a chat with our support agents so they can dig into it further.
Please sign in to leave a comment.