Visualizer Scheduled Database Refreshes Are Not Running

If your database chart updates when you click Show Chart but does not update on its recurring schedule, follow these checks.

In this article

• Check the Visualizer scheduled action
• Manually run one action as a diagnostic
• If the action is missing
• Check for a congested background queue
• Set up a real cron job for long-term stability

Check the Visualizer scheduled action

On WordPress 5.5 or later, Visualizer uses Action Scheduler when it is supported. During ordinary requests, it checks that a refresh trigger still exists and recreates a missing successor after an interrupted run.

On WordPress versions before 5.5, Visualizer uses WP-Cron as a compatibility fallback. The fallback uses the same visualizer_schedule_refresh_db hook, but it does not appear under Tools → Scheduled Actions. Use the following Action Scheduler steps only when Action Scheduler is supported.

1. In WordPress admin, open Tools → Scheduled Actions.
2. Search for visualizer_schedule_refresh_db.
3. Check the action status:
   • Pending: Waiting in the queue. Run one pending action manually to test the refresh.
   • Overdue/past due: The action missed its run time, usually because background processing did not dispatch on time.
   • Failed: The action ran and returned an error. Open the action log and fix the reported error before retrying.
   • Missing: The action was not registered.

Manually run one action as a diagnostic

Run one pending visualizer_schedule_refresh_db action from Tools → Scheduled Actions.

• If the chart updates, your query and refresh action can run.
• This is only a diagnostic or temporary recovery step. It does not fix unreliable automatic scheduling by itself.

If the action is missing

When Action Scheduler is supported:

1. Load any normal frontend or WordPress admin page. Visualizer checks for a live refresh trigger during ordinary requests.
2. Allow up to five minutes, then load another page and check Tools → Scheduled Actions again. After an interrupted run, look for a new Pending visualizer_schedule_refresh_db action; the failed action can remain in the history.

On WordPress versions before 5.5, do not expect an Action Scheduler entry. Confirm that WP-Cron can run, then follow the server cron guidance below if background events are unreliable.

If no pending successor appears on WordPress 5.5 or later, or database charts still do not refresh through the WP-Cron fallback, contact support.

Check for a congested background queue

When Action Scheduler is supported, large backlogs can delay Visualizer refreshes even when the action exists.

1. Open Tools → Scheduled Actions.
2. Check how many actions are in Pending.
3. Look for large backlogs and repeated actions generated by the same plugin.

If another plugin is flooding the queue, reduce or disable the feature creating excessive background tasks and monitor the queue again.

Set up a real cron job for long-term stability

Action Scheduler and WP-Cron both rely on WordPress background processing. Low traffic, disabled WP-Cron, or unreliable cron spawning can prevent scheduled refreshes from running consistently.

For long-term stability, set up a server cron job by following How to Set Up a Real Cron Job in WordPress.