Codebook permanently frozen on failed spawn - suspected Notebook Crash

Hi,

I had codebook fully functional over the weekend with no problems, performing some historical data pulls through Eikon and writing to csv locally. At some point, there was an API timeout and the kernel crashed. I tried reloading and now codebook won't open, it is frozen on the loading page. Every time I refresh, it goes through the initialization routine and ends up at this same result. The attached screenshot shows the log file and frozen screen. I suspect that it is trying to re-open my crashed notebook and it's getting stuck on that.

I just want to be able to log in again and get back to work. Please advise on best path forward, not sure if this requires some sort of dev side cache clearing or reset of my container image. Thanks!

Screen capture: