β Back
App #350 Β· πΊπΈ the United States
Disaster score 54Common
Marketing built a replacement for exactly one feature of SAP
Users2
Departments1
Criticality0%
Money involvedβ¬6,683/yr
βThe password is really long.ββ Kevin, Marketing
- Reason:
- Allegedly because the printer is somehow involved. Presented in a town hall as "innovation".
- Built by:
- Kevin, a recruiter
- Build time:
- one weekend
- Built with:
- a Slack bot doing database writes
- Database:
- a backup called backup-final-March.zip
- Authentication:
- the admin route is called /admin-new-final
- Deployment:
- running in Docker, but the Dockerfile is missing
- Responsible:
- "digital transformation"
- Documentation:
- a photographed whiteboard from a workshop
- Security situation:
- the firewall rule is labelled TEMP
- Future disaster:
- It will cause Security to ask "what application?".
Age: 45 days Β· originally expected to last 4 weeks Β· 2 owners so far Β· survived 1 reorganisation Β· last meaningful change 19 days ago
Rated common mostly because: 1 departments depend on it, β¬7k per year, 2 users.
Current owner
Nobody has taken responsibility for this disaster.
Claim responsibility