"Application failed to respond", but server appears to be alive and well

Today around noon Eastern our production server started serving Railway's 'app unavailable' error. We couldn't see anything wrong with the active deployment, but we told it to redeploy to try and kick things. Initial redeploy failed, so we opted to try redeploying an older commit, which deployed successfully and was reachable. On review, we're finding that the failed redeploy made it to container start, but indicated that there was no valid startup command. We had not changed any of our launch configs. We now have our most recent commits deploying successfully, as expected, but wanted to see whether anyone else has had similar issues and could perhaps point us toward a way to avoid this in the future.
Percy39d ago
Project ID: 796521e3-808a-406b-a7bd-d15d0609aaa7