Cron Pulse

It means the scheduled run time has passed but the job hasn't fired yet. This can happen when DISABLE_WP_CRON is set in wp-config.php, or when your site has low traffic and the WP-Cron system-tick hasn't triggered.

No. It fires the hook's callback functions directly without modifying the cron schedule. Use it for testing or manual one-off execution.

No. The tracker hooks fire only during cron execution (not on regular page loads) and the overhead is limited to a transient read/write per cron event.

In the WordPress options table under the key cronpulse_execution_log. The entry cap defaults to 200 and is configurable from the Settings tab (10–5000). It's cleared on uninstall.

Cron Pulse tracks jobs registered through the standard WordPress wp_schedule_event() / _get_cron_array() API. Action Scheduler uses its own queue system and is not covered.

The same way as any other WordPress REST route: a logged-in browser session (cookie + nonce), or an Application Password for external tools — Users → Profile → Application Passwords. The requesting user needs the manage_options capability.

It acknowledges the current incident for that hook so no further alert is sent for it, without turning off alerts globally. The moment the job recovers and later fails (or becomes overdue) again, alerting resumes normally for that new incident.

It's evaluated on every page load along with everything else the plugin tracks, so it only updates when you load a page — there's no background process polling for it.

Many hosts either don't have PHP's mail() function configured at all, or send through it in a way that gets flagged as spam (no SPF/DKIM alignment, generic "From" address). Configuring SMTP with your own mail provider's credentials routes through a real authenticated mail server instead, without needing a separate SMTP plugin. Use "Send Test Email" after saving to confirm it's actually working.

In the WordPress options table under the key cronpulse_email_log, capped at the last 50 entries. Each entry has the recipient, subject, type (alert/test), delivery status, and the underlying error message if it failed. Cleared on uninstall, or anytime via the Clear Email Log button.

Check the Email Debug Log on the Email Log tab. When SMTP is enabled it captures the actual SMTP conversation — connection attempt, TLS handshake, AUTH exchange, and the mail server's own response — for every send. It's a separate file under wp-content/uploads/cronpulse-logs/email-debug.log (protected from direct web access), not the options table, since a raw protocol transcript doesn't belong in the database. Login credentials are redacted before anything is written, regardless.