Result statuses and card labels
Translate what the Record Health Check card shows into the status that Flow, Apex, Platform Events, Agentforce actions, and the REST API return for the same result. People read the card label; automation must use the status.
A result reports whether a record meets a requirement. A FAIL never blocks a Salesforce save, and
it is not a Flow fault or an Apex exception.
Result statuses
Section titled “Result statuses”| Card label | Status | Meaning | What automation should do |
|---|---|---|---|
| Pass | PASS | The record meets the requirement. | Continue. |
| Failed, Warning, or Info | FAIL | The record does not meet the requirement. The label comes from the Check’s Failure Severity. | Take the business follow-up action. |
| Skipped | SKIPPED | The Check did not apply to the record, its prerequisite did not pass, or its empty-result setting skips it. | Decide whether a skip is acceptable for the process. |
| Unable to Check | UNABLE_ | Access, data, configuration, or a limit prevented a reliable answer. | Route to an administrator with the Reason Code. |
| System Error | ERROR | An unexpected problem in Record Health Check or a custom Apex Check stopped the Check. | Route for technical investigation with the Diagnostic ID. |
Setup and the API call the fourth status Unable to Evaluate (UNABLE_TO_EVALUATE); the card
shows Unable to Check.
Failure Severity
Section titled “Failure Severity”Failure Severity on a Check changes only how a FAIL looks on the card:
| Failure Severity | Card label | Color |
|---|---|---|
| Critical | Failed | Red |
| Warning | Warning | Amber |
| Info | Info | Blue |
Warning is the default. Every severity is still the status FAIL in Flow, Apex, Platform Events,
Agentforce, and the REST API, which return the severity separately as CRITICAL, WARNING, or
INFO.
Summary pills
Section titled “Summary pills”The card’s summary counts results in pills, using these labels: N Passed, N Failed, N Warning or Warnings, N Info, N Skipped, N Unable, and N System Error or System Errors. A pill appears only when its count is above zero.
Check Set status
Section titled “Check Set status”For a whole Check Set, the Flow action, Agentforce action, and REST API report the most serious status among its Checks, in this order:
ERRORUNABLE_TO_EVALUATEFAILPASSSKIPPED
A Check Set where three Checks pass and one fails is FAIL. Use the counts to tell a mixed run
from one where every Check had the same result.
Flow decisions
Section titled “Flow decisions”Check Success first, then route on Status:
| Flow output | Meaning |
|---|---|
| Success = false | The request was rejected. Read Error Type and Error Message. Status is blank. |
Success = true and Status = PASS | The record meets every requirement that applied. |
Success = true and Status = FAIL | The record does not meet a requirement. This is not a Flow fault. |
| Success = true and another status | Route SKIPPED, UNABLE_, and ERROR on paths of their own. |
| The fault path runs | A Salesforce error, such as an exhausted governor limit, stopped the action before it returned outputs. |
Never branch on message text, which an administrator can change. Use Status, the counts, and Reason Code.
Found and Expected lists
Section titled “Found and Expected lists”When Found or Expected is a list, the card shows at most 10 of its values. The rest of the list is still used for the comparison. Use the Check’s operator and counts, not the visible values, to explain the result.
When a result is unclear
Section titled “When a result is unclear”- Note the status, the Reason Code, and any Diagnostic ID shown.
- Ask an administrator to turn on Show Diagnostics for the investigation.
- Follow Troubleshoot with Show Diagnostics.