Notification email is missing
Troubleshoot missing Qubeforms notification emails. Check stored submissions, verified recipients, delivery status, spam rules, and mailbox filtering before escalation.
1. Confirm the submission was stored
Open Submissions for the correct form and check Inbox, Spam, and Archived. Match the receipt time or submission ID. A browser success screen is not proof that an email was sent. If no record exists, inspect the POST response first; a rejected request or a saved draft does not produce a final notification.
2. Check the recipient on this form
Open the form’s recipient settings and confirm the exact mailbox is verified. A profile email is not automatically a form recipient. Pending addresses do not receive normal notifications. Verify the recipient, then use a new non-sensitive test submission; do not assume verification sends every earlier message retroactively. See Verified recipients for adding or renewing verification.
3. Inspect delivery status
Open the stored submission and find Delivery status. Review its channel, status, attempts, and last error. Pending or retrying work may still be queued. Failed means its retry budget was exhausted; Cancelled means the delivery was no longer eligible. Delivered records a successful send operation, not a guarantee of placement in the recipient’s inbox. See Delivery status and retries for the queue lifecycle.
4. Check spam and routing decisions
Quarantined spam does not follow normal inbox delivery. Review its trust signals and restore legitimate messages using Not spam. That bulk action changes status and quota accounting; it does not itself send a notification. On Business, inspect routing rules that may have selected a different recipient or channel. A missing autoresponder is a separate issue: check its plan eligibility, configuration, submitter email field, and sending limits in Autoresponders.
5. Check mailbox filtering
For a delivered notification, check spam, quarantine, inbox rules, forwarding, and mailbox capacity. Search using the form name and receipt time. Ask your mail administrator to investigate the expected message if filtering is managed centrally. Notification attachments are secure download links, not file bytes attached to the email.
6. Escalate a persistent failure
If delivery remains pending unusually long or repeatedly fails, contact support through the site with the form identifier, submission ID, UTC time, channel, and sanitized last error. Avoid repeatedly submitting the customer’s message to test email. Use one separate non-sensitive test after correcting settings and confirm its outcome.
Public form keys can appear in browser code. Read keys, management credentials, and webhook signing secrets must stay on the server.