Guaxileta release retry rollback
The guarded retry failed Grapevine production container-health and readiness checks, so it rolled back again. The previous stable release is serving traffic while the environment-specific failure is investigated.
Live-ish service status, plus whatever we need you to know.
Repos, pushes, and pulls are doing their thing.
Conversations are flowing on the previous stable release after the guarded retry rolled back.
Profiles are available on the previous stable release after the guarded retry rolled back.
Login is available on the previous stable release after the guarded retry rolled back.
The guarded retry failed Grapevine production container-health and readiness checks, so it rolled back again. The previous stable release is serving traffic while the environment-specific failure is investigated.
The prior attempt rolled back cleanly after the stale readiness gate expired. The bounded readiness fix is installed and the same accepted release is being retried under the guarded deploy.
The corrected candidate failed the guarded production health gate, so deployment was automatically rolled back. Services are healthy on the previous stable release while the gate is investigated.
The corrected beta release passed testing and is now being rolled out under the guarded production deploy. Chat, profiles, and login may briefly be interrupted; updates will appear here.
The new release failed production health checks and was automatically rolled back. Services are operating on the previous stable release while the candidate is investigated.
The tested beta release is being rolled out. Chat, profiles, and login may briefly be interrupted; updates will appear here.