Why is my production application that was healthy in production returning 404s when a rollback deploy fails?

I originally had a healthy application deployed to Digital Ocean Apps. I created a new deploy, which failed. This caused a rollback deploy to occur. This rollback also failed.

about 9 hours ago
Automated rollback after failed deployment of "073dc20c-3910-42ca-aaeb-4c47c545ef3f"
about 9 hours ago
Commit 6c543f6 pushed to

At this time the live production app starts throwing 404s and is effectively taken offline. I am now forced to do a manual deploy to get my app running again.

Why is this the default functionality for deploys? I have health checks for a reason. My production containers should never be touched unless the deploy is successful. Is this not the case? If so it needs to be made very clear in big bold letters everywhere.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer