> 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/manage-episodes/update-several-episodes-in-one-request.md).

# Update several episodes in one request

Preview and apply independent metadata updates to as many as 50 episodes.

Use one bulk request for a reviewed set of episode changes inside one podcast.

## Before you start

* Filter and inspect the intended episodes.
* Confirm that every episode belongs to the same podcast.
* Prepare one attribute object per episode.
* Prepare one stable idempotency key for the whole set.

## Update the episodes

1. Build `updates` with 1 to 50 unique episode IDs and their intended attributes.
2. Preview `bulk_update_episodes` with the podcast ID and `dry_run: true`.
3. Review the episode count, each title, ID, and normalized attribute set.
4. Confirm one preview for the complete batch.
5. Submit the same batch with `dry_run: false`, the confirmation, and the same idempotency key.
6. Review `updated_count`, `failed_count`, and every per-episode result.
7. Read back updated episodes.
8. Correct and retry only failed items in a new reviewed request.

Each episode is updated independently. A validation failure on one episode does not roll back the successful updates to the others.

## Expected result

Every requested episode reports `updated` or `failed`, and partial failure is visible.

## If the preview is rejected

Remove duplicate IDs, IDs from another podcast, or more than 50 updates. Correct collection replacement fields before you request a new preview.

## Next step

[Verify that a change had the intended effect](/documentation/start-here/ai-agents/make-changes-safely/verify-that-a-change-had-the-intended-effect.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/manage-episodes/update-several-episodes-in-one-request.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.