Campaigns

Pause sending and resolve an uncertain attempt

Stop new work, investigate the evidence and choose a deliberate recovery action.

Free and Pro4 min readVersion 1.0.10
01

Pause new work

An administrator can turn off Allow email sending in Settings. A sender can pause a journey or use the relevant campaign controls. A pause stops new work; it cannot recall a message already accepted or cancel an in-flight transport call.

Do not delete queue rows or restore an older database to clear a warning. That can remove evidence of an attempted send and create duplicates.

02

Find the uncertain attempt

In Reports, inspect Uncertain attempts. A request interrupted after contacting the provider may have sent the message even if WordPress did not record a response. Check the provider or server records for that recipient and attempt.

Overview health observations help locate waiting or stalled work. A recent worker observation is not proof that every future scheduled run or external provider is healthy.

03

Record the outcome

Choose Review for the queue item. Use Cancel, Provider confirms acceptance or Retry according to the evidence. Retry requires acknowledging the possibility of a duplicate email. Unknown is not the same as failed.

For Pro, Automation trigger retries lists recent unfinished captured events. Queue retry rechecks current consent and the captured workflow revision. A failed trigger is different from an uncertain message already handed to transport.

04

Resume carefully

Recheck content, production identity, sender settings and audience before resuming. Required approvals and subscriber preferences still apply. For an A/B campaign, unresolved sample deliveries can hold automatic winner selection; do not retry samples simply to force a winner.

Keep a record of the decision and watch subsequent progress at a conservative pace.