A Gravity Form submission has come through, the entry shows up in your dashboard, and nothing has landed in your inbox. That gap between “submitted” and “I know about it” is where leads go cold, support tickets get missed, and bookings sit unanswered.
The good news is that Gravity Forms notifications rarely break in dramatic ways. The cause is almost always one of a handful of usual suspects, and you can work through them in about thirty minutes without touching code.
Why Gravity Forms Notifications Stop Arriving
Gravity Forms notifications are the emails your form sends when someone hits submit. They work by handing the email off from WordPress to your web server, which then passes it to the recipient’s mail server for delivery. Every step in that chain is a place where something can go wrong.
The submission itself almost always succeeds. The entry is stored in your database the moment the form is sent, which is why you can still see submissions inside Gravity Forms even when no email has arrived. What fails is the delivery, not the form.
That distinction matters. If entries are being recorded but notifications are not arriving, your form is fine. Your email path is the problem.
Step 1: Check the Notification Is Actually Turned On
Start with the most common cause. Someone has disabled the notification, or it was never enabled in the first place.
Open the form in Gravity Forms, then click Settings, then Notifications. You will see a list of every notification configured for that form. To the left of each name is a toggle. Green means active. Grey means off.
If the toggle is grey, that is your problem. Turn it on, submit a test entry, and check your inbox.
While you are there, click into each notification and check the Send To field. This is where notifications are dispatched. By default, Gravity Forms sends them to the admin email set in WordPress, which is often a generic address nobody monitors. Update it to the address that should actually receive submissions.
Watch for typos. We have lost count of the times a notification was being sent to info@compnay.com instead of info@company.com. Read the address out loud if you have to.
If the notification uses Conditional Logic, check those rules carefully. Conditional logic only sends the notification when certain field values are met. A rule set to “only send if Department equals Sales” will silently swallow every other submission.
Step 2: Check Your Spam Folder
Notifications often look suspicious to spam filters. They are sent from your own domain to your own domain, with subject lines like “New form submission” and content that came from a stranger. That is a recipe for filtering.
Open your spam folder. Search for the form name or the subject line set in the notification. If you find the emails sitting in there, mark them as Not Spam and add the sender address to your safe senders or contacts list.
Spam folders empty themselves on a schedule, so even if you find old notifications, send a fresh test submission to confirm the fix has taken.
Check the Junk and Other folders too if you are on Outlook or Microsoft 365. Microsoft sorts mail into more categories than Gmail, and notifications often end up in Other rather than the inbox.
Step 3: Make Sure the Inbox Itself Is Working
Before assuming the form is broken, confirm the inbox can receive any mail at all. Send a normal email from a personal account to the notification address. Wait two minutes. Did it arrive?
If nothing arrived, the form is not the problem. The mailbox is. A few likely causes.
- The mailbox is full
- The account has been suspended or moved
- DNS records for the domain are misconfigured
- The mail server is down or rejecting messages
Contact whoever manages your email hosting. They can check the server logs and tell you exactly what is happening. This is not something to try to fix from inside WordPress.
If your test email did arrive, the mailbox is fine. Move to the next step.
Step 4: Test With an Address on a Different Domain
This is the single most useful diagnostic in the whole list. Add a Gmail or Outlook.com address as a second recipient on the notification, alongside your normal one.
Submit a test form. Watch both inboxes.
There are three possible outcomes, and each one tells you something different.
Both addresses receive the notification. Your form is working correctly. The original problem was probably a spam filter or a typo, and the test you just ran has fixed it.
Only the Gmail address receives it. The form is sending mail, but something is going wrong between your web server and your own mail server. This is the classic “same-domain delivery” problem, and we cover it below.
Neither address receives it. WordPress itself is not sending the email. Skip ahead to the SMTP section, because the issue is upstream of mail delivery.
Step 5: Fix the Same-Domain Delivery Problem
This is the trickiest one, and it catches a lot of sites.
If your website lives on a hosting server that also handles your email, mail sent from the website can get confused on its way to your inbox. The server sees an email “from” your domain, looks for the mailbox locally, does not find what it expects, and either drops the message or sends it to the wrong place.
The fix involves cPanel, so only do this if you are comfortable in there. If not, send this section to your hosting provider and ask them to check it for you.
Inside cPanel, find MX Entry or Email Routing. You will see two settings that matter:
- Email Routing with options for Local Mail Exchanger, Remote Mail Exchanger, or Automatically Detect
- An MX Record that points to where mail for your domain should go
If your email is actually hosted elsewhere, for example, with Google Workspace or Microsoft 365, Email Routing must be set to Remote Mail Exchanger. If it is set to Local or Automatic, the server tries to deliver mail to itself instead of routing it to the real mail provider.
Switch it to Remote, save the change, and send a test submission. Most same-domain delivery problems resolve at this point.
Two warnings. First, only change this if you are certain your mail is hosted elsewhere. Setting it to Remote when mail is actually local will break email entirely. Second, DNS changes can take time to propagate. Give it up to thirty minutes before deciding the fix did not work.
Step 6: Install an SMTP Plugin
If notifications are not reaching any address, on any domain, WordPress itself is the problem.
WordPress sends mail through a function called wp_mail(), which by default uses the web server’s PHP mail function. That function is unreliable. Many hosting providers block it outright because it is a common spam vector. Even when it works, the messages it produces lack the authentication that modern mail servers expect, which means they get filtered.
The fix is to route WordPress mail through a proper SMTP service instead. SMTP is the standard protocol for sending email between servers, and using it makes your form notifications behave like normal business email rather than something cobbled together by a web server.
You will need two things.
- An SMTP plugin for WordPress, such as WP Mail SMTP or FluentSMTP
- A mail-sending service to connect it to, such as your existing Google Workspace, Microsoft 365, SendGrid, Mailgun, or Postmark
Install the plugin, connect it to your chosen service, send a test email from the plugin’s built-in test tool, then send a test form submission. If the plugin can send mail, but the form still cannot, you are back to checking notification settings.
Most sites benefit from running SMTP regardless of whether they currently have problems. It improves deliverability across the board, including for password resets, order confirmations, and any other email WordPress generates.
Step 7: Check Your Domain’s Authentication Records
If notifications are being sent, leaving your server, but getting rejected or filtered by recipient mail servers, the issue is likely with your domain’s authentication records.
There are three records to check. Your hosting provider or IT support can verify these for you.
SPF says which servers are allowed to send mail on behalf of your domain. If your SMTP service is not listed in your SPF record, mail from that service may get rejected.
DKIM signs your emails cryptographically so the recipient can verify they really came from your domain. A missing or broken DKIM signature is a common reason for notifications going to spam.
DMARC tells receiving mail servers what to do when SPF or DKIM checks fail. A strict DMARC policy with broken SPF or DKIM will cause your mail to be rejected outright.
If you are not seeing notifications and your tests show mail is leaving your server but never arriving, ask your IT support or hosting provider to check these three records. Fixing them is fast once someone with access knows what to do.
Step 8: Check the Gravity Forms Logging
If you have worked through everything above and still have no notifications, turn on Gravity Forms logging.
Go to Forms, then Settings, then Logging. Enable logging for Gravity Forms Core and Notifications, set the log level to Log all messages, and save.
Submit a test form, then go back to the logging page and view the log. The log will tell you exactly what Gravity Forms tried to do, whether the email was handed off successfully, and what error it received if not.
The log entries are technical, but they often point straight at the cause. “Email sent successfully” means the problem is downstream, with the recipient’s mail server. “Email failed to send” with an error message tells you what to investigate next.
This is also useful information to send to your hosting provider or developer if you need to escalate. A specific error message saves everyone time.
When to Stop Troubleshooting and Get Help
There is a point where DIY troubleshooting stops being efficient. If you have worked through the steps above and still cannot get notifications working, you are probably looking at one of three things. A server-level mail configuration problem, a DNS authentication issue, or a plugin conflict.
All three of these need someone who works on the server itself, not just inside WordPress. That is either your hosting provider, your IT person, or your web agency.
Lost form submissions cost real money. Every day notifications are broken is another day of leads, bookings, or support requests sitting in the database with nobody reading them. If form notifications are critical to your business, get them fixed properly rather than living with a workaround.
Next Steps
Work through the checks in order. If you find the cause in the first few steps, run a final test submission to confirm everything is working, then leave the form alone.
If you have worked through every step and notifications are still missing, the next move is to get someone with server access involved. That might be your hosting provider, your IT support, or a web agency that handles WordPress maintenance. Send them the log output from step eight and a summary of what you have already tried to save an hour of back-and-forth.
If you are still building out your site or thinking about a rebuild, our WordPress Development team builds forms and notification flows that work from launch. And if you want to know more about why we use WordPress in the first place, our take is in What is WordPress and Why Should I Use It?.
Talk to us about your website.
