If Formidable Forms saves an entry but the notification never arrives, trace the configured email action before changing DNS or installing another mail plugin. Storage, action execution, provider delivery, and inbox placement are separate outcomes.
Submit one clearly labeled test with a mailbox you control. Record the form name, page URL, timestamp, and entry reference. Use harmless values, not an actual customer's personal information, while investigating.
Verify the Correct Form and Event
Open the form's Actions & Notifications settings and inspect the email action. Check whether it runs on entry creation, an update, successful payment, or another supported event. A test that only creates an unpaid entry will not prove a payment-triggered email is broken.
Review conditional logic and recipient routing. Compare the saved field values with the rule's expected values, including empty answers. After duplicating a form, confirm that dynamic recipient references still point to the intended fields.
The official notification documentation covers action configuration, sender behavior, and delivery troubleshooting. A provider's authenticated sender may replace a dynamic From address, so examine the actual message identity rather than assuming the form's text is what was sent.
Separate No Action From No Delivery
| Evidence |
Next step |
| No saved test entry |
Investigate submission validation and storage first |
| Entry exists, no matching mail event |
Check trigger, conditions, and recipient resolution |
| Mail error or provider rejection |
Read the exact error and verify configured transport |
| Provider accepted it, mailbox empty |
Inspect delivery events, quarantine, and recipient rules |
Logging a mail call does not prove inbox delivery. Conversely, an empty log is inconclusive if logging was disabled or expired before the test. Correlate the same timestamp and recipient through the systems available to you.
Explanatory evidence sheet. Record your own observations.
Make a Controlled Routing Test
On a safe copy, change only the failing action's destination to a fixed mailbox you control. Keep its trigger and test answers documented. If that arrives but dynamic routing does not, inspect recipient resolution instead of rebuilding the entire email transport.
If no notification arrives, compare a transport test with an actual form submission. A successful SMTP test says the connection worked for that test message; it does not prove the form's action ran. Use the general WordPress email diagnosis for transport and sender-authentication checks.
Avoid Duplicate Recovery Mail
Do not repeatedly edit real entries or replay payments just to force a notice. Those actions may trigger additional email, CRM, or fulfillment work. Formidable's automation documentation also distinguishes delayed actions from immediate execution, so check scheduled behavior when relevant.
Once repaired, send one test through each intended routing branch and verify the recipient and Reply-To behavior. Document whether missed notifications need a controlled resend. Keep any temporary logs restricted and remove unnecessary personal data according to your retention policy.
For a repeatable failure, provide the action settings with sensitive fields redacted and the test reference when asking for Formidable troubleshooting help.
Sources checked September 27, 2026. Examples and diagrams are explanatory, not customer measurements.