Signal sends registration details to your other systems, like Zoom, ON24, Salesforce, Eloqua, Marketo or a webhook. Most of the time this just works. When a record doesn't make it across, a Signal Replay report lets you send it again without asking anyone to register again.

Why a record might not have gone through

• The other system was down or slow when the registration came in.
• The connection's login details or token had expired.
• The registration's status wasn't tagged for the flow, so Signal skipped it.
• A field the flow requires, like the email address, was blank.
• A webinar was deleted or delinked and linked again, so registrants need to be sent to the new one. See Delete/Delink Webinars from your Event or Sessions.

Signal tries a failed record again on its own, up to three times. After that it shows as Retried Abandoned under Metrics > Troubleshooting in Signal and won't be sent again unless you replay it. Records skipped because of an untagged status are never retried. See Signal Alerts - Common Errors and Recommendations.

Create a Signal Replay report

1. In your event, go to Reports and click Add Report.
2. Name the report.
3. In Report Type, pick one from the Signal Data Replay Reports group (see the list below).
4. Click Save. You can add columns and filters like any other report, which helps you find the right people.

Don't see the Signal Data Replay Reports group? Contact Support with your event code.

Which report type to pick:

• Signal Replay Registrations: one row per registration.
• Signal Replay Registrations with Webinar Details: adds the webinar details, for event-level webinars.
• Signal Replay Registrations Session: one row per session registration.
• Signal Replay Registrations Session with Webinar Details: adds the webinar details, for session-level webinars.

Replay the records

1. Run the report.
2. Tick the box next to each person who needs to be sent again. The replay only runs for the rows you tick.
3. Open the mass action list next to Filter, pick the resync that matches the flow that failed (see the list below), and click Go.
4. Check Metrics > Troubleshooting in Signal to confirm the records went through.

Which resync to pick:

• Trigger resync for Registration Create/Update flows: for flows that run when a registration is created or changed.
• Trigger resync for Registration Status Change flows: for flows that run when a registration's status changes.
• Trigger resync for Registration Event Engagement flows: for flows that send engagement data.

FAQ

Who can run a replay?

Anyone with access to the event's reports. If your team uses Signal, whoever was trained on your flows is the best person to run it.

Will people get duplicate emails or registrations?

A replay sends the record to your connected system again. How that system handles a repeat depends on its setup, so replay only the records that failed.

Next step: Records still failing after a replay? Contact Support with the event code, the flow name and a registration code that failed.