-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dashboard (or insight) fails to load #6285
Comments
I haven't watched the video. Couple of clarifications though: Is this consistent? How to repro? Mind sharing a link? |
No. You can perform the same action and sometimes it loads fine. Other times it fails.
See video. If you click around enough it'll eventually happen.
See video. Any dashboard should do. |
A bit of refactor went into insights recently. This may help with some of the issues, however it probably won't solve the "error on all items" error. Can you open the Chrome devtools network tabs and share what "Fetch/XHR" type requests fail and with what kind of response? |
Ping @leggetter for help here. Are you still experiencing this? |
I can't repro specifically this right now... but I'm tethered to my phone and on a slow connection so the dashboard insights were showing as having no matching events and suggesting I make edits while still loading So currently distinguishing the difference between a dashboard/insight before it has finished loading and when it has finished and is empty is confusing... |
Bug description
I quite frequently have problems where either an Insight or Dashboard does not load. In this case, the dashboard does not load.
Expected behavior
The Dashboard or Insight should load.
If the error is caused by a network issue of some sort (but, as mentioned, this happens a lot) then a different message in the center of the screen may be better.
How to reproduce
The following video shows the Dashboard as empty. However, it should not be empty.
posthog-failed-to-load.mp4
Environment
Additional context
Thank you for your bug report – we love squashing them!
The text was updated successfully, but these errors were encountered: