Why did someone receive the wrong event confirmation?

A Form Submitted trigger without a form filter runs for every form submission in the account, so a registration for one event can fire another event's workflow and send that event's confirmation.

1. Open Automations > Workflows and find the workflow that sent the email.

2. Open the Form Submitted trigger and filter it to the specific event form. If the workflow should cover several forms, select all of them: multiple selections combine with OR behavior.

3. Confirm the workflow is Published, not Draft.

Payment workflows can fire the same way. Check any Payment Received trigger's filters, especially Payment Source, Sub-Source, Global Product, Payment status, and the product or price. Also check Order Submitted workflows: this trigger sits under Payment triggers and carries the purchased order data. Using Form Submission Triggers and Common automation mistakes cover trigger filters in detail.

Cloning a form copies its bell notification settings, so the copied form can keep the previous event's staff recipients, autoresponder content, or PDF-recipient configuration. A submission to the new form then sends the old event's emails.

1. Open the copied form in Sites > Forms and go to the Notifications tab.

2. Update Email notification and Auto responder for the new event: recipients, subject, and content.

Common Form Mistakes lists this among the checks to run after cloning a form.

The Notifications tab in the form builder holds two emails: the Email notification, which goes to staff, and the Auto responder, which goes to the submitter. Each has its own Subject, reply-to, sender name, and optional Send form submission as a PDF setting, so either one can carry another event's wording or recipients. In older form layouts, a bell icon opens the same notification panel.

1. Open the event's form and go to the Notifications tab in the form builder.

2. Check the Auto responder first, since it emails the submitter: confirm the subject, content, reply-to, and sender name describe the current event.

3. Check the Email notification for the same details, since staff alerts go to its recipients.

Email notifications in forms and surveys explains each setting.

A link copied from a previous event registers the person under the old event's form, which sends the old event's confirmation. Ask which link the registrant used, or check the submission's URL metadata to see where the submission came from. Then confirm the link you shared points at the current event's form or event page; if you duplicated an event or a form, share the new one's own link.

Beta event emails are configured per event at Portal and Groups > Events: open the event, then Settings > Notifications. For attendees holds the registration confirmation and reminder emails, For organizers holds the new-registration alert and the Daily Summary Email, and Sender settings holds the event's From email and From name. Check the settings on the event whose confirmation was sent.

The Event Registration workflow trigger can be filtered to a specific event, ticket type, registration status, or check-in details. Check that the filter matches only the event in question; Automatically tag an event registrant or checked-in attendee shows how the trigger filters work.