Skip to content
Suggest a correction

Decide when to use Record Health Check

Getting started5 min read

Record Health Check shows people whether an existing Salesforce record meets a set of requirements and explains what to correct, without preventing a save. Compare it with Validation Rules, Duplicate Rules, and Flow to choose the right tool for a business requirement.

Record Health Check never blocks a save. It evaluates a record that already exists, and a failed Check does not undo or prevent a change. If the requirement is “Salesforce must refuse to save this record,” use a Validation Rule, a record-triggered Flow with a custom error, or an Apex trigger.

Ask whether Salesforce must prevent the save, or whether it should allow the save and then show what needs attention. Use save-time automation to prevent. Use Record Health Check to guide, especially when the answer depends on related records or must also cover records that already exist.

PropertyValidation RuleDuplicate RuleRecord-triggered FlowRecord Health Check
When it runsWhen a record is savedWhen a record is created or editedWhen a record is created, updated, or deleted, before or after the saveWhen the record page opens or a user selects Run, or when Flow, Apex, or an agent calls it
Can it block the save?YesYes, or it can allow the save with an alertYes, with a custom errorNo. A Check never updates or blocks the record it checks.
Data it can readThe record being saved and fields on its parent recordsThe fields in the Matching Rule, compared across existing recordsThe record being saved and anything the Flow queriesThe record, its parent records, related records, aggregate totals, two independent queries, or custom Apex logic
Covers records saved before the rule existedOnly when each record is saved againOnly when each record is saved againOnly if you build a scheduled or manually started FlowYes. The card checks a record when someone opens it or selects Run. The packaged Batch job checks up to 2,000 known records, and your own Batch class can check every record a query finds.
Where the result appearsAn error on saveA duplicate alert or error on saveAn error on save, or the changes the Flow makesA card on the Lightning record page, or a typed result in Flow, Apex, Agentforce, or REST
Where you configure itObject Manager → Validation RulesSetup → Duplicate Rules and Matching RulesFlow BuilderSetup → Custom Metadata Types, and Lightning App Builder for the card
Levels of resultBlocks or allowsBlocks, alerts, or allowsWhatever the Flow is built to doPass; Failed, Warning, or Info; Skipped; Unable to Check; System Error
Business requirementUse
“Salesforce must never save an Opportunity without an Amount.”A Validation Rule or a required field
“Warn about a likely duplicate Lead before it is saved.”A Duplicate Rule
“Stop this Case from saving unless a value calculated by automation is set.”A record-triggered Flow with a custom error, or a Validation Rule for a plain formula
“Show whether this Account has had a Task or Event in the last 90 days.”Record Health Check with a query or Apex Check
“Show whether an existing Opportunity is missing an Executive Sponsor Contact Role.”Record Health Check with a query Check
“Compare open pipeline with a target that comes from a second query.”Record Health Check with Compare two queries
“Apply a scoring rule that a formula or a single query cannot express.”Record Health Check with Verify with Apex
“Show a link and instructions to fix the record, but still let the user save.”Record Health Check

Other Salesforce features solve related needs:

FeatureUse it forWhere to configure it
Required fieldA value that every save must includeSetup → Object Manager → [Object] → Fields & Relationships → [Field]
Path and Guidance for SuccessCoaching text for each stage of a recordSetup → Path Settings
Dynamic FormsShowing or hiding fields and sections based on record valuesLightning App Builder
List views and reportsFinding and monitoring groups of records that match criteriaThe object’s list views, or the Reports tab

A Validation Rule, a blocking Duplicate Rule, or a Flow custom error stops every matching save until the rule is fixed. A Check that cannot run does not affect saving. The card shows Unable to Check or System Error for that Check with a message, and users keep working while an administrator corrects the configuration or access. The underlying status, UNABLE_TO_EVALUATE or ERROR, and a reason code that names the cause are available to Flow, Apex, and authorized diagnostics.

The two approaches work well together:

  1. A Validation Rule or record-triggered Flow enforces the minimum that every save must meet, such as an Account Industry.
  2. A Check Set reviews the broader picture when someone opens the record, such as Contact coverage, recent activity, and open high-priority Cases, and links the user to each fix.

A Check can read the same fields as a Validation Rule without conflict, because a Check result never changes what Salesforce allows to be saved.