> 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/help-center/ai-agents/distribution-is-not-complete.md).

# Distribution is not complete

Separate Podigee distribution state from one-time handoffs and external platform state.

Check the show state and the episode delivery state separately. Also separate a Podigee submission from what an external directory currently displays.

## Check the show

1. Call `get_distribution_status` for the podcast.
2. Read each normalized status. Do not treat the presence of a platform row as a submission.
3. Treat `not_submitted` as the default state, not as a failure.
4. Do not treat `active` as proof of submission. It can be a web-player setting.
5. Use direct submission only for a platform that Podigee marks as directly supported.
6. Follow the one-time handoff when the platform owns the listing account.

## Check one episode

Call `get_episode_distribution` for the episode. This shows delivery state for that episode and can differ from the podcast's listing state.

## Expected result

Each platform has a clear next action: submit through Podigee, complete a one-time account handoff, wait for review, correct a rejection, or verify the external listing.

## External boundary

Podigee can report the state that it controls or has received. It cannot guarantee when an external directory updates its public page. Verify the directory separately when a user needs current external proof.

## If distribution remains blocked

Send Podigee Support the podcast or episode ID, platform key, normalized state, submission or handoff time, and sanitized error. Do not send platform passwords.


---

# 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/help-center/ai-agents/distribution-is-not-complete.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.