Beta Health score out of 100 Free and open source
Flow Health Checker
Score every active Flow out of 100, and see exactly which ones will bite you.
Runs entirely inside your org. Flow metadata is read and scored in place; nothing is sent to CronCoders or any third party.
View source on GitHub Book a setup call
The problem
Flow is where the org's business logic quietly ends up, and nothing in Salesforce grades it. DML inside a loop, a hardcoded ID, a missing fault path — none of it fails a deploy, all of it fails in production, usually during a data load.
Most teams find out which Flows were badly built at the worst possible moment.
Who it is for
Salesforce admins and architects inheriting an org, preparing for an audit or a release, or trying to work out which of a hundred Flows to fix first.
Scanning an org's active Flows and working through the failures by severity.
What it does
One number for the whole org
Run it, get a score, fix the reds.
- Scans every active Flow in the org automatically
- Health Score from 0 to 100 percent, where 100 means no violations found
- Errors are weighted three times as heavily as Warnings, so the score tracks real risk
- Scan summary shows Flows scanned, Errors, Warnings, Health Score and Flows affected
Errors — the ones that break production
Five rules that fail in real orgs, usually under load.
- DML in Loop
- Hardcoded ID
- No Fault Path
- Recursive Subflow
- Subflow Fault Path
Warnings — the ones that cost you later
Eight rules covering maintainability and hygiene.
- Duplicate DML
- Hardcoded URL
- Missing Description
- No Trigger Config
- Too Many Elements
- Too Many Screen Fields
- Unconnected Element
- Unused Variable
Findings you can act on
Every violation names the element, not just the Flow.
- Severity, rule, affected Flow element and a description of the issue
- Per-Flow Error and Warning counts with an overall status such as Critical or Needs Review
- Search scanned Flows by name, and filter by All, Error, Warning or Info
- Expand or collapse an individual Flow, or expand and collapse everything at once
- Open the affected Flow directly from the scan results
Track it over time
A score is only useful if you can watch it move.
- Previous scan results are stored
- Review the history of scans and track whether the org is getting better or worse
Install it
Typical setup time: About 10 minutes.
Before you start
- My Domain enabled on the org
- System Administrator access to install a package and assign permission sets
- View All Data or equivalent access to read Flow metadata
Get the package
Install in a sandbox Install in production Deploy from source
Install in a sandbox first. Promote to production once you have tested it there.
After installing
- Install the package into a sandbox
- Assign the packaged permission set to the admins who need it
- Open the app and run your first scan
- Work the Errors list first — they carry three times the weight of Warnings in the score
What it touches
- Data
- Runs entirely inside your org. Flow metadata is read and scored in place; nothing is sent to CronCoders or any third party.
- Editions
- Developer, Trial, Enterprise, Unlimited
- License
- MIT
- Distribution
- Unlocked Package
Questions people ask before installing
What does the Health Score actually measure?
It is calculated from the Errors and Warnings found across your active Flows, with Errors weighted three times as heavily as Warnings. A score of 100 percent means no violations were found. It is a relative measure for tracking an org over time, not an absolute grade.
Does it change my Flows?
No. It reads Flow metadata and reports on it. Every fix is yours to make, and the results link straight to the affected Flow.
Does it scan inactive or draft Flows?
It scans active Flows, which is where production risk lives.
It is not on the AppExchange. Is that a problem?
It means the package has not been through the Salesforce security review. The source is public so you or your security team can read it, and you should install it in a sandbox first.
Can I add my own rules?
The rule set is open source. Fork it, add a rule, or open an issue on the repository if you think a rule belongs in the default set.
Want it running without doing it yourself?
The software is free. Paid installation, configuration and support are available.