Short and sweet. This issue is when Sense updates the web app, and the cache-clearing app in the backend (stuff you aren’t supposed to see) doesn’t do its job. That means that part of a cached website tries to load a missing piece of the webpage that no longer exists, which causes either of these (or some other) errors.
We are aware of this error, and I’ve discussed it this morning with the web dev. It looks a little worse than it is, and once the cache is cleared or the page is reloaded will resolve it. It doesn’t affect how Sense works, just some initial access. We are working to ensure everyone sees less (or preferably none) of these in the future.
The good news is that you know we are updating the website .