How PRO monitoring runs and what it stores
The 5-minute cycle, how soon you are told about each kind of problem, what PRO saves, and for how long.
On this page
How it runs
Once the license is active, PRO schedules one background job every 5 minutes using Action Scheduler (bundled with WooCommerce). That job runs each monitor in turn, then calculates the Checkout Health Score. If one monitor fails, the others still run.
Two kinds of information come in:
- Captured as it happens: a completed or failed payment, a plugin activation, deactivation or update, and the reports sent by checkout visitors’ browsers (JavaScript errors and speed).
- Judged on the 5-minute cycle: turning what was captured into an issue, or resolving it.
How soon will I be told?
| Problem | What decides the delay |
|---|---|
| Payment failures | The failures are recorded when they happen. The issue is raised on the next 5-minute cycle. |
| JavaScript error | Raised on the next cycle after the report. Escalation needs repeats at least 5 minutes apart. |
| Stuck payments | Orders are judged after they are 15 minutes old, and checked at most every 10 minutes. The silent-gateway signal looks at 24 hours. |
| Plugin conflict | At least 2 hours after the plugin change. |
| Slow checkout (Core Web Vitals) | Needs at least 3 visits in 24 hours. Each report arrives when a visitor leaves the page. |
| The email about an issue | Sent when the monitoring cycle or scan that found it finishes, in one email if several issues were found together. Never more than 10 a day. |
| Scan-based checks (shipping, coupons, theme) | At the next automatic scan (every 15 minutes by default), or when you scan manually. |
So PRO is not instant. Expect a few minutes for most problems and hours for a plugin conflict.
What it depends on
- WordPress background tasks (cron). On a quiet site, or one where WP-Cron is disabled without a real server cron, the 5-minute job can stall. The Overview then shows “Monitoring is delayed”. See Monitoring shows “delayed” or “waiting”.
- Your site being up. PRO runs inside your site, so it can’t alert you if the site is down.
- WooCommerce, for the checkout monitors.
- Working email, for issue emails and the weekly summary. They use WordPress’s normal mail sending.
- The free plugin and an active license.
What PRO stores
Monitoring data is saved in your own WordPress database, in one table (kodenzo_ch_pro_monitoring_events), and none of it is sent to Kodenzo. It holds:
- Payment outcomes: gateway name, and the time from order creation to the result.
- JavaScript errors: the message, file, line and type.
- Plugin changes: the plugin name, file and version.
- Checkout speed samples: up to three numbers and a mobile or desktop flag.
- A score snapshot each cycle.
- A monitoring log: one row each time a monitor evaluates something, with the numbers it looked at and its verdict (no customer details).
It also saves issues (with the free plugin’s issue storage) and a few settings. Stuck Payments Monitoring reads only order counts and stores no order details.
How long it is kept
| Data | Kept |
|---|---|
| Core Web Vitals samples | 60 days, then removed automatically |
| The monitoring log | 30 days, then removed automatically |
| Other monitoring events (payments, JavaScript errors, plugin changes, score snapshots) | Not removed automatically in this version |
| Scan history | The number of days set in Settings → Scan history retention. Active issues are never removed. |
On uninstall, PRO’s data is removed only if the free plugin’s Delete data when uninstalling option is on. Deactivating a license keeps the data.
Still need help?
Search the docs first — or open a ticket and our team will pick it up from the Support screen.