Short answer
First check whether the form entry, booking, or appointment was stored. A missing email does not mean the underlying record is missing, and sending the form or booking repeatedly can create unnecessary duplicate work.
If it was a Drecha Forms submission
- Open Drecha Forms → Entries and find the entry.
- Check whether its status is Spam. Spam entries do not queue notifications.
- Open the entry and inspect its queued jobs and email attempts.
- Confirm that the notification is enabled and has a valid recipient.
- If a terminal job failed, correct the recorded mail error before selecting Retry.
- If jobs stay Pending, check WP-Cron and configure a real server cron trigger on a low-traffic site.
Forms stores the entry before it queues email. A logged “Accepted” result means WordPress handed the message to its configured mail transport; it does not prove inbox delivery.
If it was an event booking or appointment
- Open the Events booking or appointment manager and confirm that the record exists.
- Check the customer's saved email address and the booking status.
- Check the log provided by the site's mail or SMTP plugin at the same time.
- Send that mail plugin's own test message.
- Test again with a controlled booking on staging after the transport is fixed.
Events Free sends its core booking and appointment messages directly through WordPress wp_mail(). It does not currently provide the same per-message delivery log and general retry queue as Drecha Forms.
Check WordPress mail delivery
- Use one configured SMTP or transactional-mail plugin, not two competing mail plugins.
- Use an authenticated sender address permitted by the provider.
- Check Spam, Junk, Quarantine, and provider suppression lists.
- Verify SPF, DKIM, and DMARC with the domain or mail provider.
- Test a second recipient at another mail provider.
Drecha does not run an SMTP server. Both plugins use the WordPress mail system and benefit from the transport already configured for the website.
When should I ask the customer to submit again?
Only after confirming that no entry, booking, or appointment exists. If the record exists, preserve it and solve the notification problem separately.
For a missing Forms entry, use the public validation or REST error to diagnose the original request. For a missing Events booking, check capacity, expiry, rate-limit, and availability messages before retrying.
Continue with the detailed guides
Use the Knowledge Base navigation on this page to open these linked guides:
- Troubleshoot missing Drecha emails and delayed notifications.
- Configure and troubleshoot email notifications.
- Fix rejected Drecha Forms submissions and file uploads.
- Fix missing events, full bookings, and unavailable appointment times.
Help us improve
Was this article helpful?
Share a quick, anonymous rating.
Continue learning