DMSI Webhooks uses Action Scheduler to process deliveries asynchronously. Queue problems are one of the most common causes of delayed or missing deliveries.

Checking Queue Status #

From WordPress Admin #

1. Go to Tools > Scheduled Actions (requires Action Scheduler)
2. Search for dmsi_webhooks_deliver
3. Review pending, completed, and failed jobs

From DMSI Webhooks Settings #

1. Go to DDLS > Webhooks > Settings
2. Check the Queue Status indicator

Queue Is Paused #

If the queue is paused, deliveries will pile up in the pending state but not execute. Paused deliveries re-queue every 60 seconds, so they are not lost — but they will not be processed until the queue resumes.

To resume:

1. Go to DDLS > Webhooks > Settings
2. Click Resume Queue

Action Scheduler Is Not Installed #

If Action Scheduler is missing, a warning admin notice is shown in WordPress admin. Webhook delivery scheduling will silently fail — events will fire but no deliveries will be enqueued.

Fix: Install Action Scheduler as a standalone plugin, or activate WooCommerce (which bundles it).

WP-Cron Is Disabled #

Action Scheduler relies on WP-Cron (or a real system cron) to process its queue. If define('DISABLE_WP_CRON', true) is set in wp-config.php, scheduled jobs will not run automatically.

Fix: Either remove DISABLE_WP_CRON or configure a server-side cron job to call WP-Cron:

/5    * wget -q -O - https://your-site.com/wp-cron.php?doing_wp_cron > /dev/null 2>&1

Deliveries Are Delayed #

If deliveries arrive late (minutes rather than near-real-time), the WP-Cron execution frequency may be low. On low-traffic sites, WP-Cron only fires when a visitor loads a page.

Set up a server-level cron job to call WP-Cron on a regular schedule for reliable delivery timing.

Related Topics #

• Troubleshooting Overview
• Troubleshooting Failed Deliveries
• Settings Reference