> 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/distribute-a-podcast/resolve-distribution-states-and-failures.md).

# Resolve distribution states and failures

Diagnose show and episode distribution states without repeating a successful handoff.

Start with show-level status, then inspect one episode only when the show is already set up.

## `not_submitted`

* Submit directly when the platform key is supported and manual submission is false.
* Complete the one-time handoff when manual submission is true.
* Treat the default row as pending setup, not as a system failure.

## `submitted` or `in_review`

Wait for the platform review. Keep the submission date and platform key. Do not submit the same show again.

## `rejected` or `deactivated`

Read `status_reason`. Podigee might not receive the platform's reason. Check the platform dashboard or contact Podigee Support with the podcast ID, platform key, and current status.

## Show is live but one episode is missing

1. Inspect the episode's publication and media state.
2. Check direct episode delivery.
3. If `feed_only` is true, verify that the episode appears in the RSS feed.
4. Wait when Podigee reports an automatic retry.
5. Preserve the last error and timestamp for a failed direct delivery.

## Expected result

You identify the responsible boundary and take one targeted action without duplicate submission or publication.

## Next step

[Understand what Podigee can verify outside Podigee](/documentation/start-here/ai-agents/distribute-a-podcast/understand-what-podigee-can-verify-outside-podigee.md).


---

# 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/distribute-a-podcast/resolve-distribution-states-and-failures.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.