What happened
A recent deployment introduced a configuration issue that impacted a subset of our services. Normally, our deployment process automatically rolls back when issues are detected. In this case, the affected services didn’t fail completely on startup, so the rollback wasn’t triggered.
Impact
How we resolved it
We identified the problem and manually rolled back the deployment, which restored full functionality.
What we’re doing to prevent this
We’ve identified why the issue didn’t trigger an automatic rollback, and we’re planning improvements to our startup checks. These changes will ensure immediate rollback in the future.