Case Study: How One Checkbox Triggered a Major Incident

Some Salesforce bugs come from code.
Some come from automation.
This one came from the most dangerous thing in every project:

A checkbox no one understood.

The Incident
A Sales Manager reported:

“All our discounts disappeared. Every Opportunity now requires executive approval.”

This was not good.
This was the definition of “wake up the team NOW.”

Discount approvals had been stable for months.
Nothing in production had changed.

Or so we thought.

The Hidden Mechanism
Deep inside a Flow lived a condition:

IF(HighRiskCustomerc = TRUE, requireApproval = TRUE)

Simple.

Except someone had updated a customer segmentation integration,
and the incoming payload now set High_Risk_Customer__c = TRUE
for every single customer.

Overnight.

Without warning.

Automation didn't break.
Automation did exactly what it was told.

Users screamed.

Why It Was Hard to Trace
Because:

• The checkbox wasn’t visible on the page layout
• No one remembered it existed
• No one knew automation depended on it
• The integration change wasn’t communicated

Classic Salesforce horror story.

The Fix

We exposed the checkbox temporarily.
Set all customers back to safe.
Updated the integration mapping.
Added a guardrail in Flow.
Then hid the checkbox again.

But we also did something more important:

We documented the field.

The Lesson

In Salesforce, unused fields don’t stay unused.
Someone, somewhere, someday will repurpose them.

The real danger is not automation.
The real danger is:

“Fields that nobody remembers but everything depends on.”

Final Thoughts

Whenever you see a mysterious checkbox,
don’t ignore it.

Behind every checkbox in Salesforce
is either a small feature
or a nuclear bomb.

Treat both with equal respect.