Connection failed with status 410

My Spaces repo stopped working with the unhelpful message “Connection failed with status 410, and response Your space is on error, check its status on” [sic]. The solution was to clear cookies on my browser. I’m finding clearing cache to be a solution to other odd problems. I’m wondering if this is related to streamlit caching? If my colleagues run into these issues, it will be a show stopper, no matter how much I attempt to document the issue.

Anyone know how to mitigate cookie issues?

My users have also reported seeing this same error message today on my streamlit space built for the AI vs AI soccertwos competition.

The app has only a single function using @cache_data which caches 5MB of data. Similar to @bsalita, the error apparently disappears when switching to a private browsing window / clearing cookies.

1 Like