Ah yes, agreed, it would be much better to explain what happened to the user as well. 
At the moment, the continuation expiry just triggers a page reload.
I'm sure we can get a user-visible message across one way or another. I filed When redisplaying pages after continuation expiry, include a user visible error message · Issue #81 · racket/racket-pkg-website · GitHub to track that.