A saved entry and a successful confirmation do not by themselves prove email delivery. Open the entry's notification/action information to inspect the result of each planned task. The detail page shows recent runs and the recovery controls that apply to their state.
Understand the status
| Status | Meaning |
|---|---|
| Queued | Saved and waiting for a worker. |
| Running | Claimed for processing; external effects may already be underway. |
| Sent | For email, WordPress mail returned success. This means acceptance by the mail layer, not confirmed inbox delivery or reading. |
| Failed | Preparation failed, the handoff reported a failure, or a recovery limit was reached. Read the diagnostic before acting. |
| Blocked | A compatible provider or payload version is unavailable. Restore the provider before considering retry. |
| Unknown | Execution began but its result is uncertain. An email may already have been sent. |
| Skipped | Conditions did not match, a sending limit applied, or an extension prevented it. It is not simply waiting in the queue. |
| Canceled / Expired | The work was canceled or its retained payload expired. It is not automatically revived. |
Retry the retained attempt
Retry, when offered and eligible, queues the same run with its retained prepared payload. It does not rebuild the email from today's field answers, subject, recipient or conditional rules.
Use it only when that original prepared message is still the intended one and the underlying issue has been addressed. An unavailable provider or missing payload can make Retry inappropriate. Some add-on providers have their own recovery rules and acknowledgement requirements.
Resend current data
Resend creates a new intent from the entry's current answers and the form's current enabled action configuration. It rechecks applicability and conditions. Use it deliberately when a corrected answer or notification configuration should be used.
An uncertain earlier outcome may have already reached the recipient. Check before resending. Read and acknowledge the possible-duplicate prompt when shown. A running attempt must finish or reach a known state before another resend is allowed.
Saving an entry or changing a notification is not a resend. Some add-on actions run only when their specific event occurs; use the controls offered for that provider rather than assuming every action supports a submission-style resend.
Cancel and retention
Cancel removes retained pending payload where allowed. It cannot recall an email or external action that has already started. Trashing an entry also cancels pending notifications; restoring it does not restart those sends.
Sent, canceled, skipped and expired payloads are purged immediately. Other retained payloads expire after seven days; queued or blocked work becomes Expired rather than being sent late. Safe terminal metadata normally expires after thirty days during maintenance, with some event records retained with the entry to prevent replay.
If background work is delayed
Check Email sending mode, the website's loopback requests and cron. Process pending actions deliberately executes a due batch across the site. It can send mail, so review pending work first.
For Sent without an inbox result, check the address, spam filtering and mail transport. Repeatedly resending cannot diagnose delivery by itself.
