Step-by-step guide
Step-by-step guide
Follow this sequence from installation to a working Check. Complete each step in a sandbox and move on after confirming the expected result.
First working Check
Section titled “First working Check”| Step | Do this | Stop when… |
|---|---|---|
| 1 | Understand what the framework does | You can explain the difference between a Check Set and a Check |
| 2 | Install and verify it in a sandbox | A normal user can see the Record Health Check card |
| 3 | Explore the installed examples | One installed Check Set runs on a record page |
| 4 | Create your first Check | Your own Check shows both a passing and an attention state |
| 5 | Add and activate the card | The intended app users can open and run it |
| 6 | Configure a complete Check Set | Every Check has been tested with representative users and records |
Do not test only as a System Administrator. A card-only tester needs Record Health Check Card User; an automation user needs the permission set for the way it runs checks. Every runner also needs access to the records and fields the Check reads.
Choose your next path
Section titled “Choose your next path”Build more Checks
Section titled “Build more Checks”- Choose the Evaluation Type.
- Copy the closest Formula, Query, Compare Two Queries, or Apex example.
- Add a safe fix link when users need a next action.
- Understand result labels and statuses.
Run from Flow
Section titled “Run from Flow”- Prove the Check Set on the card first.
- Run it from Flow.
- Use
Successfor request handling andStatusfor the health decision.FAILis not a Flow fault. - Leave event publication as
NONEunless a separate process must receive the result.
Save history or notify another process
Section titled “Save history or notify another process”- Decide whether you need Platform Events.
- Start with Check Set run summaries when counts are enough.
- Save events to an organization-owned object if you need lasting history.
- Test duplicate delivery and failure handling before activation.
Go to production
Section titled “Go to production”- Back up the configuration.
- Review security and data access.
- Follow the production operations checklist.
- Keep troubleshooting available to support owners.
Extend with code or agents
Section titled “Extend with code or agents”Start in Developer guides. Administrators can skip that folder unless they are handing an Apex, background-job, Agentforce, MCP, or external event task to a developer.
Resolve a problem
Section titled “Resolve a problem”| What you see | Start here |
|---|---|
| The card is missing or has the wrong Check Set | Add the card to a record page |
| A result is unexpected | Troubleshoot Record Health Check |
| A status or Reason Code is unclear | Look up exact behavior |
| Flow does not branch as expected | Flow action inputs and outputs |
| A receiving Flow gets no event | Save or send results after a run |