Skip to content
Suggest a correction

Uninstall Record Health Check

Getting started5 min read

Remove the Record Health Check package from a Salesforce org without leaving broken record pages or automation. Back up the configuration your organization created, remove every dependency in a safe order, uninstall the package, and confirm that nothing still refers to it.

Uninstalling deletes the package’s two Custom Metadata Types, so every Check Set and Check in the org is deleted with them, including the ones your organization created. It also deletes all Record Health Check Readiness records. Back up the configuration first. You cannot undo an uninstall except by installing the package again and restoring the backup.

You need the Salesforce Download AppExchange Packages permission to uninstall a package.

Find everything that depends on Record Health Check:

  1. Lightning record pages. In Setup, open Lightning App Builder, open each record page for the objects your Check Sets use, and list every page that contains the Record Health Check component, with its activation assignment.
  2. Flows. List Flows that use the Run Record Health Check, Run Record Health Check Set, or Validate Record Health Check Configuration action, or that start when a Record Health Check Set Run, Record Health Check Result, or Record Health Check Log Platform Event is received.
  3. Apex. List Apex classes and triggers that use the rhc namespace, such as classes that call rhc.RecordHealthCheck.evaluate or implement rhc.RecordHealthCheckPlugin, and their test classes.
  4. Scheduled jobs. In Setup → Scheduled Jobs, list jobs created with rhc.RecordHealthCheckScheduled.
  5. Agents and integrations. List Agentforce agents that use the Record Health Check actions, and integrations that call the Record Health Check REST resource or the MCP server.
  6. Permission Set assignments. Record the users assigned to each of the seven Record Health Check Permission Sets: Card User, User, Admin, Diagnostics Viewer, MCP Integration, Error Log Publisher, and Readiness Auditor.

Follow Back up and restore configuration to retrieve every Record Health Check Set (rhc__Record_Health_Check_Set__mdt) and Record Health Check (rhc__Record_Health_Check__mdt) record your organization created. Open the retrieved files and confirm that every Check Set and Check you expect is there.

Store the backup with the list of record pages, automation, and Permission Set assignments. If Record Health Check is reinstalled later, these let you restore the same setup.

The configuration backup does not include Record Health Check Readiness (rhc__Record_Health_Check_Readiness__c) records, the receipts saved when a draft Check passes Preview. Uninstalling deletes them. To keep them as a record of past verification, export them first: in Setup, open Data Export, select Export Now, select Record Health Check Readiness, and start the export.

For each page you listed:

  1. Open the page in Lightning App Builder.
  2. Select the Record Health Check component and delete it.
  3. Select Save.

Removing the card first means users see the page without the card, instead of an error during the uninstall.

Step 3: Remove automation that depends on the package

Section titled “Step 3: Remove automation that depends on the package”
  1. Deactivate each Flow you listed. Then delete the Flow versions that reference Record Health Check, because Salesforce can block the uninstall while any Flow version, even an inactive one, references a package component.
  2. Delete each scheduled job you listed in Setup → Scheduled Jobs.
  3. Remove Record Health Check actions from Agentforce agents, and stop integrations that call the REST resource or the MCP server.
  4. Delete or change each Apex class and trigger that references the rhc namespace, including test classes. Deploy the change before you uninstall.

In Setup → Permission Sets, open each Record Health Check Permission Set, select Manage Assignments, and remove its users. The uninstall also removes these Permission Sets, but removing assignments first gives you a clear record of who had access.

  1. In Setup, enter Installed Packages in Quick Find, then select Installed Packages.
  2. Next to Record Health Check, select Uninstall.
  3. Review the list of components that Salesforce will delete.
  4. Select the confirmation checkbox, then select Uninstall.

If Salesforce reports that the package cannot be uninstalled, it lists the components that still depend on the package. Remove those dependencies as described in Steps 2 and 3, then try again. Do not delete unrelated metadata to force the uninstall.

To uninstall with the Salesforce CLI, find the installed 04t ID first, then uninstall it:

Terminal window
sf package installed list --target-org ORG_ALIAS
sf package uninstall --package INSTALLED_PACKAGE_VERSION_ID --target-org ORG_ALIAS --wait 30

Replace INSTALLED_PACKAGE_VERSION_ID with the ID that the first command lists for Record Health Check, and confirm the org alias before you run the second command.

Result: Installed Packages no longer lists Record Health Check. Salesforce can finish the uninstall in the background and send a confirmation email.

What to checkExpected result
A record page that had the cardThe page loads without errors, and Lightning App Builder no longer offers the component.
Setup → Custom Metadata TypesRecord Health Check Set and Record Health Check are gone.
Setup → Apex ClassesNo class from the rhc namespace remains.
Setup → Permission SetsNo Record Health Check Permission Set remains.
Setup → Scheduled JobsNo job runs rhc.RecordHealthCheckScheduled.
Flows, Apex, agents, and integrationsNothing refers to Record Health Check actions, classes, or Platform Events.

To bring Record Health Check back:

  1. Install the package as described in Install Record Health Check in a sandbox.
  2. Deploy the Check Sets and Checks from your backup.
  3. Assign the Permission Sets to the users you recorded.
  4. Add the card back to the record pages you recorded.
  5. Restore the Flows, Apex, scheduled jobs, agent actions, and integrations you removed.
  6. Run each card with a passing record and a failing record, as a user with normal access.