DocumentationConnections and delivery
Free / Pro

Resend stored submissions after a delivery problem

Repair a destination, understand the resend scope and verify queued submissions without creating new leads.

On this page

Before you start

You need permission to manage WConvert, a working destination and the original saved submissions. The destination’s required edition and service plugins must be available. Keep the relevant campaign published with the destination attached while recovering delivery.

If the lead is missing, resolve missing submissions first. A resend cannot recover a record already erased or removed by retention.

Repair the cause first

  1. Open Settings → Connections & destinations and read the destination’s warning.
  2. Review Actions → Recent sends. A Will retry entry already has another attempt scheduled.
  3. Fix the reported problem: for example, reconnect the same account, restore its access or repair the site’s mail transport.
  4. Save the destination, then send a controlled test.

Restoring the original route is different from choosing another account or list. WConvert may leave older submissions out when destination settings have changed since capture.

Queue the saved submissions

  1. Open the destination’s Actions menu.
  2. Choose Send stored submissions again. A destination warning may also offer Send again.
  3. Read the confirmation. It states whether the selection starts at the last successful send or includes every eligible stored submission.
  4. Choose Send again once. Read the queued count and any records left out for review.
Confirmation showing the scope of a destination resend Enlarge screenshot
This example has no earlier success, so the dialog describes every eligible stored submission for this destination.

Confirmation showing the scope of a destination resend

Confirmation showing the scope of a destination resend

Zoom to inspect the controls. Press Escape to close.

Understand which records can be sent

The resend uses original submission details from campaigns whose published version uses the destination. It creates delivery jobs, not new leads. Availability, stored routing details and later account/list/settings changes can prevent an older record from being eligible.

If the result says a run reached its limit, let that batch finish before considering another. Read any “left out” explanation; repeatedly clicking the action will not repair an incompatible route.

Verify recovery

  1. Reopen Recent sends after background processing. Check that the new attempt is accepted rather than only queued.
  2. Use View submission to confirm which saved record it came from.
  3. Check the receiving service or mailbox. Confirm any expected list, field or download link.
  4. Check that the Leads list has not gained a new submission solely because of the resend.
Recent sends with an accepted attempt following an earlier retry Enlarge screenshot
Recovery is confirmed by the accepted attempt and the receiving service, not by the number of history rows.

Recent sends with an accepted attempt following an earlier retry

Recent sends with an accepted attempt following an earlier retry

Zoom to inspect the controls. Press Escape to close.

The saved lead and the new delivery attempt are separate records. Confirm the final result in the receiving service before treating recovery as complete.

Still stuck?Tell us where you got to

Include your WConvert version, the page you tested and any error message.