Why is the dashboard stuck on the loading spinner?

Almost always a network or cache issue, not data. Hard reload first, check status, then sign-out/in and clear cache. 30-second triage inside.

~3 min read All users

What's happening

The Overture event dashboard waits for three things before it renders: your auth session, the org context, and the event itself. If any one of those takes too long, you see the spinning loader. The good news: it's almost always a network or cache issue, not a data problem.

30-second triage — try these in order

  1. Hard reload the page.
    • Windows / Linux: Ctrl + Shift + R
    • macOS: Cmd + Shift + R
    This bypasses the browser file cache. About half of all spinner reports clear on a hard reload.
  2. Check your connection. Open any other website. If that also hangs, it's your network. Switch networks (move from Wi-Fi to phone hotspot, for example) and try again.
  3. Check the Overture status. See How to check Overture's live system status. If we're red, you'll see it there and you can stop debugging — it's on us.
  4. Open a new tab and go to app.overture.show. If the login page loads fine but the dashboard hangs, it's a per-event problem. Try opening a different event from the same org. If that one works, it's specific to the first event — send us that event name.
  5. Sign out and back in. A stale auth session is the second most common cause. Sign out from the door icon in the top toolbar, then sign back in.
  6. Clear local cache if the spinner persists. See How to clear Overture's local cache safely.

What's almost never the cause

If nothing fixes it

Capture this and send it to [email protected]:

See How to report a bug to support for the bug-report format we like.