This seems like it happens sometimes if you quickly skip through the end of an encounter. I’m working on trying to figure out why. Thanks for the report though! In your browser, you can quickly reload the page to fix this though.