Use Gravity Forms' Resend Notifications action on the existing entry when you need to send an email again. Submitting the public form a second time creates a different event and can duplicate records or trigger integrations. A notification resend is also not a general-purpose replay of every add-on feed.
Decide whether resending is appropriate
If the original message never arrived, first use the notification troubleshooting guide to identify whether the problem was eligibility, addressing or delivery. Sending again before correcting the cause usually produces another failure, or several delayed duplicates.
If the request is simply to provide an authorized recipient another copy, confirm which notification they need. One entry may have an internal staff notification and a separate customer confirmation. They can contain different information and should not be treated as interchangeable.
Select one entry and one intended notification
The official resend instructions describe this administration workflow:
- Open the correct form's Entries list.
- Select the single intended entry.
- Choose Resend Notifications from the actions menu and apply it.
- Select the required notification in the options window.
- Review the optional Send To override before confirming the resend.
The override can replace recipients for that operation. Treat it as a data-sharing decision, not a harmless debugging field. Do not route a real entry containing customer details to a personal mailbox just to see whether mail works.
Content: Current values and links reviewed. Privacy: Destination is authorized. History: Previous resend checked. Result: Inbox and message ID matched. Explanatory checklist, not a customer test result.
Review what today's message will contain
Check whether the entry or notification configuration has changed since the original submission. A resend should not be assumed to reproduce the exact historical message byte for byte. Use a controlled entry to verify the installed setup when merge tags, conditional recipients or time-sensitive links matter.
For example, a confirmation may contain an expired appointment link while the stored entry is otherwise correct. Fixing delivery alone will not make that link usable. Review attachments and download links with the same care.
| Pre-send check |
Why it matters |
| Entry ID matches the request |
Prevents sending another person's submission |
| Notification name is correct |
Separates customer and internal content |
| Recipient is authorized |
Avoids accidental disclosure |
| Links are still valid |
Prevents a delivered but unusable message |
| Prior resend is recorded |
Reduces duplicate team actions |
Verify delivery and leave an audit note
Record the time and selected notification. Match any available mail-provider message ID to delivery events and confirmation from the intended inbox. A UI success message is not the same as observed receipt.
Do not assume that resending email updates a CRM contact or reprocesses a payment. Those are separate integration tasks. If a corrected entry needs a CRM update, review the feed behavior before replaying anything.
For a larger resend request, agree on recipients and scope first, then test a small controlled sample. HandL WP can help repair the notification path without turning a mail issue into a duplicate-entry or privacy problem.
References reviewed October 7, 2026. Examples are explanatory, not customer test results.