Approvals are a review step before sending. The Content Outbox follows planned work and delivery history. These are different parts of a publication’s journey.
Before it goes
If a route requires approval, review its source, destination, and prepared message in the Approval queue. Check current permissions and the intended timing before using the available approval action.
Follow the result
- Pending: work may still be waiting for timing, approval, permissions, a running scheduler, or an available provider.
- Confirmed: use the specific recorded receipt and current result to understand what succeeded.
- Not sent: use a reviewed safe retry only when offered for the unsent work.
- UNKNOWN: the provider may have accepted the request. Inspect that exact step and receipt before resolving it.
When something is waiting
Check capture and dispatch pauses, approval, current grants, encryption keys, provider availability, delivery windows, quotas, and the scheduler. If WordPress itself has not published a scheduled post, investigate its core cron runner first.
Ask for help with the useful details
Export the sanitized report from Diagnostics and review it before sharing. Include the plugin version, environment versions, sanitized error codes, UTC timestamps, and synthetic reproduction steps. Exclude tokens, private content, raw requests, and configuration secrets.
Customer recovery guide; APPROVAL_QUEUE_151.md, OUTBOX_UX_151.md, SUPPORT_DUMP_151.md.