PRO Features
PRO thresholds reference
Every default threshold, window and limit in Commerce Health PRO in one place, and which ones you can change.
On this page
This page lists the defaults PRO uses. Only a few of these can be changed in settings; the rest are fixed values in this version. The last column says which.
How often things run
| What | Default | Can you change it? |
|---|---|---|
| Background monitoring cycle | Every 5 minutes | No |
| “Monitoring is delayed” warning | No check for more than 20 minutes | No |
| Stuck Payments order checks | At most every 10 minutes | No |
| Continuous Diagnostics (automatic scan) | Every 15 minutes | Yes: PRO settings (5 minutes to 30 days; shortest effective is 5 minutes) |
| Checkout Health Score | Recalculated every 5 minutes; 14-day trend; change compared with about 24 hours earlier | No |
| License check | Once a day, and whenever the PRO license screen is opened | No |
| Weekly summary email | At most once every 7 days, on by default | Yes: PRO settings (on/off) |
Payment Gateway Monitoring
| Setting | Default | Result |
|---|---|---|
| Window | Last 60 minutes, per gateway | |
| Fewer than 3 attempts | Any failure | Low |
| Failure rate | Under 10% / 10% to under 20% / 20% to under 25% / 25% or more | None / Low / Medium / Critical |
| Slow checkout | Average of 8 seconds or more | Medium |
| Resolves | When below thresholds, or no activity in the window |
Stuck Payments Monitoring
| Setting | Default | Result |
|---|---|---|
| Orders not judged yet | Younger than 15 minutes | |
| Current window | Orders created 75 to 15 minutes ago | |
| Usual share (baseline) | Previous 7 days up to 2 hours ago; needs at least 10 orders | |
| Unfinished spike | At least 3 unfinished, 30% or more, at least 2 times the usual share | Medium |
| Severe spike | At least 5 unfinished, 50% or more, at least 3 times the usual share | High |
| Critical spike | At least 8 unfinished, 75% or more, at least 4 times the usual share | Critical |
| Not enough history | 3 unfinished and 50% / 5 unfinished and 60% / 8 unfinished and 75% | Medium / High / Critical |
| Silent gateway | Orders in the last 24 hours with none paid or failed: 3 to 4 / 5 to 9 / 10 or more | Medium / High / Critical |
| Skipped gateways | Bank transfer, cheque, cash on delivery | More can be skipped by a developer filter |
| Cancelled orders examined | Up to 100 per window |
JavaScript Error Detection
| Setting | Default | Result |
|---|---|---|
| Times an error was recorded | 1 / 2 / 3 or more (no time window) | Low / Medium / Critical |
| Same error stored | At most once every 5 minutes | |
| Issue resolves | After 30 days without the error | |
| Reports accepted | 20 per minute per visitor address; the script sends at most 10 per page load | |
| Text length | 300 characters per field |
Plugin Conflict Detection
| Setting | Default | Result |
|---|---|---|
| When a change is judged | At least 2 hours after it happened | |
| Compared | The 2 hours before with the 2 hours after | |
| A new JavaScript error appears | Never seen in the 2 hours before | Medium |
| Payment failures rise | By 2 or more | Critical |
| Resolves | Only when you click Mark as resolved |
Checkout Performance (Core Web Vitals)
| Metric | Good | Poor |
|---|---|---|
| LCP | 2.5 s or less | over 4 s |
| INP | 200 ms or less | over 500 ms |
| CLS | 0.1 or less | over 0.25 |
| Setting | Default | Result |
|---|---|---|
| Alert window | Last 24 hours, 75th percentile, at least 3 visits | |
| Poor | Critical (at most once per metric per 24 hours; High if it re-crosses within that time after dipping to Needs improvement) | |
| Needs improvement | Medium | |
| Good | Issue resolves | |
| Performance screen look-back | 7 days, or 30 days if fewer than 5 visits | |
| Samples kept | 60 days | |
| Reports accepted | 10 per minute per visitor address |
Scores and ranking
| What | Default |
|---|---|
| Checkout Health Score deductions | Payment Gateway: Low 8, Medium 20, Critical 40. Stuck Payments: Medium 10, High 25, Critical 40. Cart and Checkout Page: Medium 10, High 30, Critical 45. JavaScript Error: Low 4, Medium 12, Critical 25. Plugin Conflict: Medium 10, Critical 25. |
| Health screen bars | Start at 100, minus Critical 40, High 25, Medium 12, Low 4 per active issue |
| Recommendations | Score = severity (Critical 100, High 75, Medium 50, Low 25) × multiplier (payment, stuck payments and cart/checkout page 1.3, shipping 1.2, JavaScript error 1.1, plugin conflict 0.9, others 1.0). 75 or more is High impact, 40 or more is Medium; lower is not listed. |
Issue emails and the monitoring log
| What | Default | Can you change it? |
|---|---|---|
| Lowest severity emailed | High (so High and Critical) | Yes: PRO settings, Issue Emails (Low, Medium, High, Critical only, or Off) |
| When an issue emails | When it is new, reopened, or its severity rises. Never for an unchanged issue, and never for Info | No |
| Subject | [Site] [SEVERITY] Commerce Health: title, or “N issues need attention” with a breakdown when several arrive together | No |
| Resolved email | Sent when a monitor sees an issue clear and PRO had emailed you about it. Not sent for an issue you were never emailed about, or for a scan finding from the free plugin | No |
| Issue emails per day | At most 10; the last one says so | No |
| Issues listed in one email | Up to 10, then “Plus N more” | No |
| A reopened issue | Emailed as reopened at most once an hour | No |
| Monitoring log | One row per monitor check; kept 30 days; downloadable as CSV on the PRO settings screen | No |
Extra checks and licensing
| What | Default |
|---|---|
| Shipping Validation | High when a class is unpriced; up to 50 products per class |
| Coupon Validity | Low (expired or used up), Medium (broken); first 200 coupons |
| Theme Health | Critical (broken), Medium (update available) |
| Free plugin email | The free plugin alone emails a new or reopened critical finding (a plain-text email, on its Settings screen) |
| Offline grace for licensing | 3 days |
Not sure what a threshold means in practice? See What PRO can and cannot detect.
Was this article helpful?
Still need help?
Search the docs first — or open a ticket and our team will pick it up from the Support screen.