Right now if the underlying model is re-deploying, the widget just looks broken / unresponsive The network call does end up in a 503 though - we should display an error message 