Gravity Forms notifications missing? Start with the entry

Find a specific entry and its notes

Submit one test from the affected public page and find that entry in Gravity Forms. Open its details and look at Notes for notification results.

If a result indicates a successful handoff, follow the email route beyond Gravity Forms. If it reports an authentication or connection failure, preserve the exact error before making changes. Missing notes may require logging or investigation of the notification’s triggering conditions.

Check the notification that should have run

Do not use a successful test of another form as evidence that this notification is configured correctly. Forms can have different notifications and delivery behaviour.

• Is the notification enabled?
• Does its event match the action you are testing?
• Is the recipient valid, including any merge-tag value?
• Is the From address authorised for the sending route?

Test each recipient branch

Conditional logic decides whether a notification should run. Routing determines the recipient. Gravity Forms documents that an unmatched routing setup can leave a notification with no destination.

Create a small test table: answer selected, expected recipient, observed result. Include every meaningful branch, rather than only the default path. If only one department misses messages, this comparison is more useful than replacing the whole email system.

Verify more than the success banner

Once settings are corrected, repeat the exact failing submission. Confirm the entry, the sending result and the mailbox. If a transactional-email add-on handles the notification, inspect that service rather than assuming a site-wide SMTP test follows the same route.

Keep the successful test conditions with your repair notes. When fields or routing rules change later, repeat those checks before relying on the form for new enquiries.