Step 1: Check the Log Detail #

1. Go to DDLS > Webhooks > Logs
2. Find the failed delivery
3. Click to open the log detail modal
4. 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 been made?

Common Response Codes and What They Mean #

My Endpoint Returns 200 But I See No Data #

If your endpoint returns 200 immediately without processing the payload body, it may be responding before reading the request. Ensure your receiver reads and parses the body before responding.

Deliveries Are Not Arriving at All #

1. Verify the event is firing: check if a log entry with pending status was created
2. If no log entry exists, the event may not be firing in DDLS Core, or the endpoint is not subscribed to the event
3. Check Action Scheduler queue: Tools > Scheduled Actions → search for dmsi_webhooks_deliver
4. If the Action Scheduler job shows as failed, check the PHP error log

SSL Certificate Errors #

If your endpoint uses a self-signed SSL certificate or has SSL issues, DMSI Webhooks will fail with a connection error. To temporarily bypass SSL verification for testing:

1. Go to DDLS > Webhooks > Settings
2. Enable Disable SSL Verification (for testing only — do not use in production)

Related Topics #

• Delivery Status Reference
• Endpoint Disabled (410 Gone)
• Queue Issues