Start here
Choose how a Check starts
Use this page to choose the supported entry point for a Record Health Check run. Record Health Check can run on a record page or through automation you configure. It does not install a save-time trigger.
Choose the person or process that needs to start evaluation, then follow the linked guide.
Supported start paths
Section titled “Supported start paths”| Who or what starts the run | Entry point | Best for | Continue with |
|---|---|---|---|
| A person opens a record | Lightning card with When the page opens | Immediate advisory guidance on one record | Add the Lightning card |
| A person selects Run or Rerun | Lightning card with When the user clicks Run | Deliberate review of one record | Add the Lightning card |
| A Flow | Run Record Health Check Set or Run Record Health Check action | Automation that needs the result in the same Flow interview | Flow actions |
| Apex in the current transaction | rhc.RecordHealthCheck.evaluate | Code that must branch on the response immediately | Apex API |
| Queueable Apex | rhc.RecordHealthCheckQueueable.enqueue | Up to 200 known record IDs processed later | Queueable API |
| Packaged Batch Apex | rhc.RecordHealthCheckBatch.run | 1 to 2,000 known record IDs | Batch API |
| Custom Batch Apex | Your Database.Batchable calls evaluate | A query locator or custom persistence requirement | Batch API |
| Scheduled Apex | Your schedulable class or packaged scheduling helper | Recurring asynchronous evaluation | Scheduled API |
| Agentforce | Packaged Check or Check Set action | An agent that needs structured health results | Agentforce actions |
| Hosted service or MCP client | Agent REST resource | A reviewed server-side integration | Agent REST API |
Do not create new @future integrations. Move existing work to Queueable Apex.
Actions that prepare or display results
Section titled “Actions that prepare or display results”- Saving a business record without an open Record Health Check card or configured automation
- Saving a Record Health Check Custom Metadata record
- Adding the component to an App page or Home page; the component supports record pages
- Receiving a Platform Event, unless your own subscriber explicitly calls a Flow or Apex entry point
- Running a Validation Rule; Record Health Check is advisory and does not block the save
Important limits at the start
Section titled “Important limits at the start”| Where the Check runs | Limit or behavior |
|---|---|
| Lightning card | Evaluates one record and up to 25 active Checks; an oversized whole set runs none |
| Direct Apex or one Flow request group | Up to 200 records and 25 active Checks |
| One Flow action call | Up to 10 distinct Check or Check Set and Event Publication groups |
| Queueable helper | Up to 200 known record IDs |
| Packaged Batch helper | 1 to 2,000 known record IDs; automatic scope is 1–100 and is reduced when needed for the FormulaEval budget |
| Agentforce and REST | Event publication is always NONE |
Card load, record save, and Run
Section titled “Card load, record save, and Run”An open automatic card refreshes after a standard record save or RefreshView notification. A manual card does so after its first completed Run. Saving a record elsewhere does not start a background health check by itself.
Opening or refreshing a record page can evaluate the card, but a load never publishes Check Set Run or Check Result events. An explicit Run or Rerun can publish those events when the Check Set and Check publication settings are enabled. Error Log publication is a separate setting.
Every run rereads the Check Set configuration before it evaluates, so Run and Rerun pick up Setup edits without a page refresh. See Do I need to refresh the record page?.