Run a Salesforce org health check
Review usage and configuration across a Salesforce org and generate a document with findings and suggested actions. Use it to identify fields and reports to review, reassess licenses, or take inventory of older automation.
Run a health check
- Open a conversation in Blaze and select the Salesforce org to inspect from the org menu. If it is not connected yet, follow Connecting a Salesforce Org.
- Enter
/health-checkin the conversation input and send it. - Progress appears in the conversation. Expand a progress row to inspect the work currently underway.
- When the check finishes, the results open in Canvas. You can also reopen the document from its card in the conversation.
What it checks
| Area | Main checks |
|---|---|
| Users and licenses | License assignments, users who have not logged in for a long time, and related usage |
| Data and storage | Storage usage, object and custom field usage, and dependencies of low-usage candidates |
| Code and automation | Apex API versions and test coverage, plus the state of flows, Process Builder, and other automation |
| Reports and external integrations | Report usage, connected apps, and related settings |
| Lightning migration | Assets that need changes, assets to verify in Lightning Experience, and user rollout tasks |
Read the results
Move through the document page by page. Use the table of contents to open a chapter and review the overview, area summaries, individual findings, and appendix lists.
Individual findings describe what was found, the business impact, suggested steps, and how to check the result after taking action. The appendix lists fields and settings to review.
For a larger view, press Fullscreen above the document. In fullscreen, use the left and right arrow keys to change pages and Esc to return.
Low-usage fields and unused settings are candidates for review. Check their role in your business and their dependencies before deciding what to change. The document also identifies areas where data could not be retrieved, for example because of permissions.
Check Lightning migration readiness only
To focus on Lightning migration, send:
/health-check lightning-migrationReview assets that need changes, such as JavaScript buttons and S-controls, separately from assets that need runtime checks, such as Visualforce pages, and user rollout tasks.