> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/start-here/ai-agents/check-your-account-and-readiness/check-encoding-and-publication-readiness.md).

# Check encoding and publication readiness

Check whether a podcast can encode media and accept a publish request before upload.

Run a podcast-specific preflight before you upload media or publish an episode.

## Before you start

* Confirm the connected Podigee account.
* Obtain the target podcast ID.
* Know whether the planned workflow will create a draft, publish now, or schedule publication.

## Check readiness

1. Run the Podigee doctor with the target `podcast_id`.
2. Set `check_write` to `true` when the workflow will change data.
3. Confirm that the subscription is active.
4. Confirm that the podcast ID is not in `blocked_podcast_ids`.
5. Confirm that `encoding.can_encode` is `true` and its status is `ok`.
6. Confirm that `publish_readiness.ready` is `true`.
7. Review all publication blockers when readiness is false.
8. Check the encoding, storage, and episode publish allowances needed by the workflow.

## Expected result

The selected podcast can encode media, accepts a valid publication time, and has enough plan capacity for the intended workflow.

## If encoding is blocked

Confirm the subscription and encoding allowance. Select another eligible podcast, wait for a reset, or resolve the plan limit before you upload media.

## If publication is blocked

Review every returned blocker. Correct the podcast or publication inputs, then run the same check again. Do not upload or publish until the preflight succeeds.

## Next step

[Run a Podigee connection health check](/documentation/start-here/ai-agents/check-your-account-and-readiness/run-a-podigee-connection-health-check.md) again after you resolve a blocker.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/start-here/ai-agents/check-your-account-and-readiness/check-encoding-and-publication-readiness.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.