Repair the configured trigger, then run Preflight. Do not add multiple replacement triggers blindly.
Form Mule not sending emails?
Do not immediately reinstall, rerun every row, or switch products. First isolate whether the failure is trigger setup, quota, row data, template conditions, authorization, or an uncertain prior send.
This page is an independent troubleshooting guide. FormMerge is not affiliated with Form Mule or New Visions Cloudlab.
Quick answer
Do not treat a missing status as proof that nothing was sent. Verify the trigger and quota, inspect the exact row and condition, check Gmail Sent plus the recipient inbox, and only then decide whether the row is safe to retry.
Six checks before migration
- Trigger: confirm the expected form-submit or timer trigger still exists and belongs to the correct spreadsheet.
- Authorization: open the add-on and check whether Google requires the owner to authorize it again.
- Gmail quota: verify the sending account still has daily quota.
- Recipient: inspect the exact email column and the affected row for blanks, formula errors, or malformed addresses.
- Conditions: confirm the row still matches the template's send condition.
- Prior outcome: check Gmail Sent and the recipient inbox before retrying a row whose status is unclear.
See the replay and uncertain-send safety path
The controlled proof shows a logical notification remaining protected after rows move, a manual SEND_UNCERTAIN decision, the 30-day audit, and the watchdog boundary.
The privacy-enhanced YouTube player loads only after you press play. Controlled copied-sheet proof with synthetic data.
Watch the complete Form Mule failure and safe-migration tutorial
Diagnose trigger, authorization, quota, recipient and condition failures; then test exact pending preview, one-time approval, 30-day replay protection, SEND_UNCERTAIN resolution, audit and watchdog pause on a copied Sheet.
The privacy-enhanced YouTube player loads only after you press play. Controlled copied-sheet tutorial with synthetic data and test inboxes.
Match the symptom to the next safe action
A sent, sending, or uncertain fingerprint in the 30-day ledger should stay blocked until reviewed.
Check the recipient inbox, then mark verified sent, reset after the check, or keep the notification blocked.
Review the latest errors and uncertain rows before explicitly resuming automatic sending.
If you decide to migrate
Use a copied spreadsheet and one operational template. FormMerge adds exact pending preview, approval invalidation, a 30-day replay ledger, explicit SEND_UNCERTAIN resolution, audit, and watchdog health. It does not reproduce Form Mule's full conditional-template or range-function feature set, and it is not marketing automation.
FAQ
Why is Form Mule not sending?
Check trigger ownership, reauthorization, quota, the recipient cell, the template condition, and whether the row may already have been accepted for delivery.
Should every failed row be retried?
No. An uncertain outcome requires an inbox check first; a blind retry can create a duplicate notification.
Does FormMerge guarantee exactly-once delivery?
No. It prevents known replays and fails closed on ambiguous outcomes, but it does not claim provider-level exactly-once delivery.