Common Issues

Having trouble? Here are the most common issues and how to resolve them quickly.

#Events are not running on time

Symptom: Events show as overdue in the Events Manager. The health score flags schedule lag.

Cause: WordPress pseudo-cron depends on site visits to trigger. Low-traffic sites can have events fire hours late.

Fix: Set up a real server cron job via Tools > Real Cron Setup. The wizard generates the exact command for your environment.

This is the single most impactful thing you can do to improve cron reliability. Even one crontab entry that runs every 5 minutes makes a significant difference.

#Health score shows "Loopback Failed"

Symptom: The health score has a red Loopback factor.

Cause: WordPress cannot reach wp-cron.php via an HTTP request to itself. Common causes:

HTTP Basic Auth blocking cron requests
Server firewall blocking loopback connections
Incorrect WP_SITEURL or WP_HOME values in wp-config.php
SSL certificate errors on the loopback request

Fix: Test that your server can reach its own wp-cron.php URL directly:

curl -I https://yoursite.com/wp-cron.php?doing_wp_cron

A 200 response means loopback is working. Anything else indicates the cause.

#Execution Log is empty

Symptom: The Execution Log page shows no entries.

Cause: Execution Tracking is not enabled.

Fix: Go to Settings > General and enable Execution Tracking. New executions will start appearing immediately.

Historical data before enabling tracking is not retroactively available. Tracking must be on when events fire to record them.

Symptom: An addon you expected to see in the sidebar is not there.

Cause: Addon pages only appear when the addon is enabled.

Fix: Go to Addons and toggle the module on. The sidebar updates without a page reload.

#Notifications are not arriving

Symptom: Alerts are configured but nothing is received.

Fix - check in this order:

Use the Test button on the Notifications page to verify the channel delivers
Confirm the specific alert rule is toggled on (not just the global notifications toggle)
For Slack and Discord: verify the webhook URL has not been revoked or rotated
For Telegram: confirm the bot is still active and the chat ID is correct
For Email: check your server mail log or switch to an SMTP plugin like WP Mail SMTP

The Test button sends a real message through the configured channel immediately. If the test works but real alerts do not arrive, the alert rules or thresholds are likely misconfigured.

#"Cron option too large" warning

Symptom: A warning appears about the cron option in wp_options being too large.

Cause: The cron schedule has grown excessively, often due to plugins that register events without proper cleanup.

Fix: Go to Tools and run:

Orphan Cleanup - removes hooks with no registered callback
Duplicate Detector - removes extra copies of recurring events

After cleanup, the option size should drop significantly.

#Event Chain is not progressing past the first step

Symptom: A chain starts but subsequent steps never execute.

Cause: The trigger condition is not being met. For example, an "On Success" step follows a step that returned an error.

Fix: Check the Chain Log. Skipped steps are labeled Skipped and show which trigger condition was not met.

Add an Always step at the end of your chain to log or notify regardless of outcome. This makes it much easier to diagnose chain failures.

Last updated 6 Sep 2026

Was this article helpful?