> 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/make-changes-safely/verify-that-a-change-had-the-intended-effect.md).

# Verify that a change had the intended effect

Read Podigee state after a change and distinguish an accepted request from its real effect.

Read the affected Podigee record after every consequential operation.

## Before you start

* Keep the returned result or operation ID.
* Know the intended target and expected final state.
* Keep read access to the affected podcast and resource.

## Verify the change

1. If Podigee returned an operation ID, monitor it to a terminal state.
2. Read the affected podcast, episode, production, import, listener, or distribution connection.
3. Compare the current values with the approved preview.
4. Confirm that the target ID matches the intended record.
5. For publishing, verify the episode and production state, publication mode, and scheduled or published time.
6. For distribution, distinguish Podigee's handoff from acceptance by the external platform.
7. For imports, compare the imported episode IDs and any skipped items with the expected scope.
8. Record any mismatch with the operation ID and current state.

## Expected result

The current Podigee state matches the reviewed intent, and any external handoff limit is stated clearly.

## If the operation succeeded but the result looks wrong

Do not repeat the mutation. Preserve the operation ID, result, target IDs, and read-back. Check that you selected the intended account and resource. Then correct the state through a new previewed change or contact Podigee Support.

## If an external platform does not show the change

Confirm the Podigee connection or submission status first. Podigee can report that it handed work to an external service, but only that service can confirm its own processing or publication.

## Next step

[Choose a reversible action before permanent deletion](/documentation/start-here/ai-agents/make-changes-safely/choose-a-reversible-action-before-permanent-deletion.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/make-changes-safely/verify-that-a-change-had-the-intended-effect.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.