Troubleshooting

Why your Google Forms notification email is not sending

If a Google Form submission happened but no notification email arrived, the problem is usually not mysterious. It is often one of a few practical setup gaps: the wrong recipient path, the wrong respondent email source, no preflight, no test send, or no post-submit execution check.

Start with the shortest possible check

Before changing templates or rewriting your form, verify the email path in this order.

  1. Confirm the notification feature is actually enabled.
  2. Confirm at least one recipient path exists: owner, additional recipient, or respondent confirmation.
  3. Run preflight and make sure it passes.
  4. Run a test send before relying on real submissions.
  5. After a real submit, inspect the most recent notification report and execution log.
This order matters because it separates configuration problems from trigger or delivery problems.

Common reasons the email did not send

No real recipient path

The owner alert may be off, additional recipients may be empty, and respondent confirmation may also be off.

Wrong respondent email source

If the form does not collect email automatically, the confirmation flow needs an actual Email field.

Preflight was skipped

Preflight is the fastest way to catch missing recipients, missing fields, or setup gaps before launch.

Test send was never used

A test send catches template and recipient issues before you depend on the trigger path.

Nobody checked the execution state

If the email still does not arrive after a real submit, inspect the execution log and latest report.

Live trigger path still needs attention

Save and test-send style checks can look healthy while the real submit-trigger path still needs a separate check.

Related guides

Boundary: FormNotifier is a lightweight Google Forms notification add-on. It is not a full CRM, drip campaign platform, or ticketing system.