Monitoring Release returned a 503 - Deploy was actually successful

Just deployed locally to test some new Dockerfile configurations and got this strange error once the server was deployed but the release was actually successful and there was no rollback.

I also just saw this bug when changing a secret in an app which triggered a new deploy.

That’s weird. Thanks for pointing it out, we’ll monitor this.

1 Like

We had some overnight capacity issues and are spinning up more hosts specifically to help with this. You might have noticed our growing pains keep moving to different parts of the stack. :wink:

1 Like