Record Health Check Set Run event fields
Look up every field of the Record Health Check Set Run Platform Event, which reports how many Checks passed, failed, were skipped, could not be evaluated, or had a system error for one record after a run. Async jobs also publish one Set Run event when the job ends.
| Property | Value |
|---|---|
| Label | Record Health Check Set Run |
| API name in your org | rhc_ |
| Event type | High Volume |
| Publish behavior | Publish After Commit |
| Contract Version | 1. |
To save these events in a history object with Flow or Apex, see Save Check Set run summaries.
When it publishes
Section titled “When it publishes”| The run starts from | A Set Run event publishes for each record when |
|---|---|
| A person selecting Run or Rerun on the card | Publish User Run Event is selected on the Check Set. |
| A Flow action, Apex code, or an async job | Event Publication is ACTIONABLE or ALL. With ACTIONABLE, it publishes even when every Check passes. |
A run of a single Check also publishes a Set Run event per record, naming the Check’s Check Set.
When a Queueable, Batch, or Scheduled job runs with ACTIONABLE or ALL, it also publishes one
job event when the job ends. Page loads, browser refreshes, the automatic rerun after a save,
Agentforce actions, the MCP service, and Preview never publish. See
Decide when to use Platform Events for every
rule.
Salesforce delivers the event only after the transaction that ran the Checks completes. When that transaction rolls back, the event is discarded.
Fields
Section titled “Fields”| Field label | API name in your org | Type | Record event | Job event |
|---|---|---|---|---|
| Event ID | rhc_ | Text(80), required | A different value for every event | Same |
| Run ID | rhc_ | Text(120), required | The run’s ID, shared by all its events | batch- or queue- followed by the job ID |
| Phase | rhc_ | Text(30), required | COMPLETED | COMPLETED when every record was processed; otherwise FAILED |
| Check Set Qualified API Name | rhc_ | Text(80), required | The Check Set that ran | Same |
| Record ID | rhc_ | Text(18) | The record that was checked | Blank |
| Source | rhc_ | Text(30), required | What started the run | QUEUEABLE, BATCH, or SCHEDULED |
| Occurred At | rhc_ | Date/Time, required | When the event was created | Same |
| Contract Version | rhc_ | Text(10), required | 1. | Same |
| Framework Version | rhc_ | Text(20), required | 2. | Same |
| Eligible Check Count | rhc_ | Number(5, 0) | Checks the run included | Blank |
| Evaluated Check Count | rhc_ | Number(5, 0) | Results for this record: the sum of the five counts below | Blank |
| Passed Count | rhc_ | Number(5, 0) | Results with status PASS | Blank |
| Failed Count | rhc_ | Number(5, 0) | Results with status FAIL | Blank |
| Skipped Count | rhc_ | Number(5, 0) | Results with status SKIPPED | Blank |
| Unable Count | rhc_ | Number(5, 0) | Results with status UNABLE_ | Blank |
| System Error Count | rhc_ | Number(5, 0) | Results with status ERROR | Blank |
| Submitted Record Count | rhc_ | Number(7, 0) | Blank | Records submitted to the job |
| Processed Record Count | rhc_ | Number(7, 0) | Blank | Records the job processed |
Source is one of USER_INITIATED (the card), FLOW, APEX_API, QUEUEABLE, BATCH, or
SCHEDULED.
The event has no overall status field. To derive one, use the first that applies: ERROR when
System Error Count is above 0, then UNABLE_TO_EVALUATE, FAIL, and PASS for their counts, and
SKIPPED otherwise.
Example record event
Section titled “Example record event”{ "rhc__EventId__c": "rhc-api-1791387000000-9f2c41d07a3b4c6e8d15f0a-1-4e8a0c2d9b7f41a3e6c5d8b0a1f29374", "rhc__RunId__c": "rhc-api-1791387000000-9f2c41d07a3b4c6e8d15f0a2b7c94e31", "rhc__Phase__c": "COMPLETED", "rhc__CheckSetQualifiedApiName__c": "Account_Data_Quality", "rhc__RecordId__c": "001000000000001AAA", "rhc__Source__c": "FLOW", "rhc__OccurredAt__c": "2026-10-07T15:30:00.000Z", "rhc__ContractVersion__c": "1.0", "rhc__FrameworkVersion__c": "2.0.11", "rhc__EligibleCheckCount__c": 5, "rhc__EvaluatedCheckCount__c": 5, "rhc__PassedCount__c": 3, "rhc__FailedCount__c": 1, "rhc__SkippedCount__c": 1, "rhc__UnableCount__c": 0, "rhc__SystemErrorCount__c": 0}The IDs, time, and counts are examples. Account_Data_Quality is a Check Set created in the org,
so it has no prefix; an installed example Check Set has one, such as
rhc__Example_Account_Check_Builder_Guide.
Access
Section titled “Access”The Record Health Check Card User, Record Health Check User, and Record Health Check Admin permission sets grant Create and Read access to this event. Receiving automation needs Read access, plus access to any object it writes to.
The event names a Salesforce record. Protect saved copies as you protect that record.