Troubleshooting
Troubleshooting
Troubleshooting Overview
Last Updated: March 23, 2026Use this guide to diagnose and resolve common issues with DMSI Webhooks. Quick Diagnostic Checklist Before diving into specific issues, verify the following: [ ] DMSI DDLS is active [ ] Action Scheduler is installed and active [ ] Plugin license is active (check DDLS > Licenses) [ ] Target endpoint URL uses HTTPS (HTTP...
Troubleshooting Failed Deliveries
Last Updated: March 23, 2026Step 1: Check the Log Detail Go to DDLS > Webhooks > Logs Find the failed delivery Click to open the log detail modal Review: – Response Code: What did your endpoint return? – Response Body: Any error message from your server? – Error Message: Any WordPress-side error? – Retry Count: How many attempts have...
Endpoint Disabled (410 Gone)
Last Updated: March 23, 2026What Is a 410 Response? A 410 Gone HTTP response signals that the requested resource no longer exists and will not return. DMSI Webhooks treats a 410 response as a permanent signal that the endpoint URL is no longer valid. Automatic Behavior on 410 When a delivery receives a 410 Gone response: The delivery is...
Queue Issues
Last Updated: March 23, 2026DMSI 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 Go to Tools > Scheduled Actions (requires Action Scheduler) Search for dmsi_webhooks_deliver Review pending, completed, and failed jobs From DMSI Webhooks Settings Go to DDLS >...
License and Access Issues
Last Updated: March 23, 2026Deliveries Stopped — License Invalid If the plugin license expires or validation fails for more than 3 days, webhook deliveries stop. The plugin enters a grace period automatically on first validation failure. Check License Status Go to DDLS > Licenses Find DMSI Webhooks in the extensions list Check the status column Status What to Do...
