Salesforce database-script outage
A roughly 15-hour global outage occurred after Salesforce proactively blocked access to over 100 customer instances to contain the damage, at an estimated cost of millions of dollars in lost productivity.
The damage was public. The root cause was preventable.
A roughly 15-hour global outage occurred after Salesforce proactively blocked access to over 100 customer instances to contain the damage, at an estimated cost of millions of dollars in lost productivity.
What the software actually got wrong
A faulty database script deployed to production accidentally granted broad read/write data-access permissions across affected customer accounts, and Salesforce had to take large parts of its infrastructure offline to safely undo the change.
A faulty database script deployed to production accidentally granted...
A faulty database script deployed to production accidentally granted broad read/write data-access permissions across affected customer accounts
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
Salesforce had to take large parts of its infrastructure...
Salesforce had to take large parts of its infrastructure offline to safely undo the change
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.