The approval queue

The queue is where an agent's work waits for a person. Nothing in it exists on your WordPress site yet — approving is what sends it.

What you see

• The rendered content, not raw markdown, so you review what readers will see.
• The target site, the post title, the categories and tags, and any SEO fields requested.
• Which agent submitted it, and when.
• Why it is in the queue: site policy, a guardrail, or the agent asking for review explicitly.

Approving and rejecting

Approving hands the action to WordPress. The per-component outcomes come back after that, so an approved post can still land partially — a bad image URL does not become good because you approved it. Read the action in Activity afterwards if it matters.

Rejecting declines the action permanently and records it as Rejected, distinct from Failed. You can leave a note; the agent can read the state through get_post_status and try again with something different.

Notifications

The dashboard shows a badge on the approvals area and polls for new items while it is open. If you have approval emails enabled in Settings, Pressbotics also emails you when something is queued. Email is best-effort — the queue in the dashboard is the source of truth.

What can go wrong

• A scheduled post approved after its publish_at has passed. Approve early.
• An approved post showing as Published (partial). The body landed; a component did not. See Troubleshooting.
• An agent that says it published when the post is actually queued. get_post_status tells it the truth — a well-behaved agent reads it.