Fixed ThinkCodeNames returning a blank 404 page after two individually-safe deployment changes were applied together
What happens
The game briefly served the platform's default 404 page instead of loading. Two unrelated deployment settings had been changed in the same commit: automatic cleanup of removed resources was switched on, and automatic namespace creation was switched off. Either one alone is safe. Together, they leave the deployment system unable to rebuild the game's own environment if it ever disappears — every retry fails before it can recreate what it needs.
Impact
A short outage on 2026-08-09, self-inflicted during unrelated maintenance and caught in the same session.
Resolution
The environment was recreated by hand for immediate recovery, then automatic namespace creation was restored so the deployment system can self-heal again. Three other services that had received the same pair of changes were checked and corrected before they could hit it.
0 Comments
Sign in to comment
No comments yet. Be the first to share your thoughts!
