> Discover all available Postdom documentation from the machine-readable index: https://postdom.com/llms.txt

# One post. Every destination answers.

Postdom keeps one overall post state and a separate recorded outcome for every selected account. Partial success stays visible. Failure keeps its reason.

One request can publish on two accounts and fail on a third. Your agent sees all three answers.

## Every answer stays separate.

The post state summarizes the whole run. Destination states preserve what happened on each selected account.

The synthetic contract example has overall state **partial**:

- **Instagram Reels:** published — Published at 09:00:18 UTC
- **YouTube Shorts:** published — Published at 09:00:41 UTC
- **TikTok:** failed — provider_down · provider unavailable

## Read the run.

Exposed timestamps show when work was scheduled, when a destination published, and when the durable record last changed.

- **scheduled_for · 09:00:00:** The exact UTC slot Postdom was asked to hold.
- **published_at · 09:00:18:** Instagram confirms publication without changing the other answers.
- **updated_at · 09:02:14:** The failed TikTok answer makes the overall run partial.

## Partial stays visible.

A successful destination never hides a failed one. The overall state remains partial while published and failed answers coexist.

- Two destinations published
- One destination failed
- **Overall run: partial**

## Failure keeps its reason.

Postdom returns the recorded code and detail instead of collapsing the run into a generic error.

- **Code:** provider_down
- **Detail:** The provider or durable publish worker was unavailable when this publish ran.
- **Agent action:** Return the exact failed destination and reason to a human. Do not rename the state.

## Know when to stop.

The wire state tells the agent whether to keep reading, wait for review, return control, or report the recorded outcome.

- **Keep reading — scheduled, publishing:** Poll only inside the caller's configured budget.
- **Wait for review — requires_approval:** A human must resolve the individual approval decision.
- **Return control — draft, changes_requested, rejected, missed_approval, missed_schedule:** Give the exact state, post ID, and feedback to a human.
- **Report evidence — published, partial, failed:** Return the post state and every recorded destination answer.

## Exact state vocabulary.

Postdom exposes eleven post states and four destination states. Agents preserve these values exactly.

- **Post states:** draft, requires_approval, changes_requested, rejected, missed_approval, missed_schedule, scheduled, publishing, published, partial, failed
- **Destination states:** queued, sent, published, failed

## The answer survives the dashboard.

get_publish returns the overall post state, every destination publish, plan authorization, approval feedback, agent context, and exposed timestamps.

The same rules are available as raw Markdown, so an agent can read the state boundary without scraping this page.

- Runs and outcomes: https://postdom.com/docs/runs-and-outcomes.md
- Run states: https://postdom.com/docs/reference/run-states.md
- get_publish: https://postdom.com/docs/tools/get-publish.md

## Outcome questions.

### How do I know whether every platform published my post?

Read the post with get_publish. Postdom returns one overall post state plus a separate queued, sent, published, or failed state for every selected destination.

### What does a partial run mean?

Partial means published and failed destination outcomes coexist on the same post. Postdom preserves every destination answer instead of presenting the run as complete success or complete failure.

### Does Postdom retry a failed social post automatically?

A partial or failed record may reconcile after a recoverable local failure is followed by authoritative provider evidence. The read contract itself does not retry, approve, revise, or reschedule work.

### Which run states should an AI agent keep polling?

The agent keeps reading scheduled and publishing states only within its configured polling budget. Approval, recoverable, partial, failed, and rejected states return to a human with the exact post ID and evidence.

### Can an agent call a failed run action_required?

No. action_required is not a Postdom wire state. The agent must preserve the exact post and destination states and return the recorded reason without renaming either one.

## Close every run.

Give your agent one durable place to read what published, what failed, and what needs a human.