Skip to content

Choose how a Check starts

Getting started5 min read

Record Health Check runs only when a person or a process you configure starts it. Compare the supported entry points, from the Lightning record-page card to Flow, Apex, and Agentforce, and choose the one that fits who needs the result and when.

Record Health Check installs no trigger. Saving a record, receiving a Platform Event, or editing a Check in Setup never starts a run on its own.

What starts the runEntry pointRecords per requestUse it whenGuide
A person opens a record pageLightning card with When Checks Run set to When the page opens1People should see guidance as soon as they open the recordConfigure the component
A person selects RunLightning card with When Checks Run set to When the user clicks Run1People should decide when to review the recordConfigure the component
A FlowRun Record Health Check Set or Run Record Health Check actionUp to 200 per Check or Check SetThe Flow needs the result to decide its next stepFlow actions
Apex in the same transactionrhc.RecordHealthCheck.evaluateUp to 200Your code must branch on the result immediatelyRun from Apex
Queueable Apexrhc.RecordHealthCheckQueueable.enqueue1–200, one Check SetA known set of records should be checked later in one jobQueueable Apex
Batch Apexrhc.RecordHealthCheckBatch.run1–2,000, one Check SetA known list of records is too large for one transactionBatch Apex
Your own Batch Apex classYour Database.Batchable class calls rhc.RecordHealthCheck.evaluateUp to 200 per execute scopeYou select records with a query or must store results yourselfBatch Apex
A schedulerhc.RecordHealthCheckScheduled.scheduleDaily, or your own Schedulable class1–2,000, one Check SetThe same records should be checked every dayScheduled Apex
An Agentforce agentRun Record Health Check for Agentforce or Run Record Health Check Set for Agentforce action1An agent needs structured health results for one recordAgentforce actions
An external service or MCP clientThe Record Health Check Apex REST resource1A reviewed server-side integration needs resultsAgent REST API

Every entry point requires the Record Health Check Run Custom Permission, which the packaged runner Permission Sets include. The card needs Record Health Check Card User or a broader set. Flow, Apex, Queueable, Batch, Scheduled, and Agentforce callers need Record Health Check User or Record Health Check Admin. A REST caller, such as the MCP service’s integration user, can instead use Record Health Check MCP Integration, which grants only the REST resource.

For new asynchronous work, use Queueable Apex rather than @future methods.

  • A Check Set can run at most 25 active Checks. If a Check Set has more, none of its Checks run, and the card says No Checks were run.
  • One request can include at most 200 unique records. The packaged Batch and Scheduled helpers split up to 2,000 records into transactions of at most 200.
  • Formula work is limited to 95 Salesforce formula evaluations per transaction. A Formula Check uses about one evaluation per record, so a request with Formula Checks can admit fewer than 200 records. When a request would exceed the budget, Record Health Check rejects the whole request before it evaluates anything. The packaged Batch helper chooses a smaller automatic scope to stay inside the budget.
  • One Flow action call can contain at most 10 groups, where a group is one Check or Check Set with one Event Publication value. Each group can contain up to 200 records.

The platform limitations reference lists every limit and how to stay within it.

  • When the page opens: the card waits until the page is idle, for up to one second, and then runs its Checks. After a run, it shows Rerun unless the Check Set hides the button or the heading.
  • When the user clicks Run: the card runs only after the user selects Run. The Check Set must show its heading and Run button, because the heading holds the button. A Check Set that combines this setting with Card Heading Display set to Hide is invalid, and the card shows a setup error.
  • After a record save: when the record is saved on the same page, a card set to run when the page opens runs its Checks again. A card set to wait for Run runs again only if it has already completed a run.
  • After a Setup change: every Run or Rerun reads the Check Set again first, so changes made in Setup apply without reloading the page.

The card evaluates its Checks one Check at a time on the server, with up to eight Checks in progress at once on a page.

Opening a page, or a refresh after a save, never publishes Platform Events. When a user selects Run or Rerun, the card publishes:

  • a Check Set Run event, if the Check Set’s Publish User Run Event is selected; and
  • a Check Result event for each Check whose Publish User Result Event is selected.

Flow, Apex, and the asynchronous helpers ignore those two checkboxes. They publish only when the caller sets Event Publication to ACTIONABLE or ALL. Agentforce and REST requests never publish these events. Choose where results go explains each option.