← Back
App #1238 · 🇺🇸 the United States
Disaster score 380Rare
Operational Excellence built a tool for deciding which spreadsheet is current
🧟 Builder has left
Users306
Departments2
Criticality29%
Money involved€0/yr
“It's just a cron job.”— Ravi, Operational Excellence
- Reason:
- Allegedly because someone said "just add AI". With a settings page that does nothing.
- Built by:
- Ravi, an analyst
- Build time:
- one weekend
- Built with:
- a REST API generated by something nobody can regenerate
- Database:
- a database view called prod-final_FINAL_FINAL
- Authentication:
- the audit log contains passwords
- Deployment:
- behind a load balancer pointing to exactly one machine
- Responsible:
- an intern whose contract ended in September
- Documentation:
- a Confluence page linking to another Confluence page
- Security situation:
- the audit log is console.log
- Future disaster:
- It will cause Finance to ask "what is this charge?".
Accidentally connected to (3)
- → uses Google Sheets as an event log
- → depends on a folder called Final
- → posts failures into a Slack channel nobody watches
Age: 17 days · originally expected to last 14 days · 2 owners so far · survived 1 reorganisation · last meaningful change 17 days ago · original builder left 43 days ago
Rated rare mostly because: 306 users, 3 accidental connections, 29% chance of becoming business critical.
Current owner
Nobody has taken responsibility for this disaster.
Claim responsibility