When I login and switch to my home page, loading takes forever. Page only shows the grey ghost images. Sometimes it shows thumbnails in Recent Notebooks yet after a few seconds those are replaced by an otherwise blank page with the message Oops, an unexpected error occured.
When showing timeline console, timeline goes on forever (i.e. page never seems to fully load and complete).
I’d try a hard reload (in Chrome: cmd-shift-r, or shift-click the reload button, or reload while your dev tools are open and “disable cache” is checked in your network tab). If that doesn’t resolve the issue, try logging out and back in.
That could very well be. I can’t reproduce that though, as the highest version in any of my notebooks is ~2700. Reminds me of this topic:
By the way, if you want to get rid of your history (without creating a fork), and if you’re not relying on your notebook’s internal slug (e.g. by importing it), you could move your code to a new notebook by following these steps.
@dunstan The error handling on the home page could use some improvement. I can reproduce the error described in the opening post by blocking https://api.observablehq.com/user/continue-editing in DevTools. As a result the “Oops, an unexpected error occurred.” error appears.
Since each component on the homepage appears to load independently, there should be a nicer way to handle connection problems.
I’m also running into the same problem. The “Recent Activity” timeline tries to load for about 40s, then the home page gets replaced with Oops, an unexpected error occured. Tried restarting while disabling cache, logging out and back in, opening in incognito, switching to a different browser – the same issue persists. The highest version in any of my notebooks is about 1700.
After some DevTool inspection, the culprit seems to be that a request to https://api.observablehq.com/user/activity?days=7&timezone=Asia%2FHo_Chi_Minh&type=all keeps returning a 503 error. Would love for a way to fix this. Thanks
Thanks Martien. It was actually being worked on, but under another guise, as the problem raised it’s head elsewhere too. I’ll report back once we’ve tracked the issue down. (And thanks for the offer of help.)