Currently, whenever we encounter an error after loading data asynchronously, we fire a toast when we encounter an error.  Unfortunately, we also leave the UI in a bad state across the board.

We should audit all instances where a toast is fired, and come up with a (consistent) strategy for displaying both the toast and / or the error.