> 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/confirm-a-consequential-change.md).

# Confirm a consequential change

Apply the exact Podigee change shown in a valid preview and reject changed or stale requests.

Apply only the exact change that the user reviewed in the current Podigee preview.

## Before you start

* Obtain a fresh dry-run preview.
* Review the normalized action, target, values, and consequences.
* Keep the same connected user and Podigee account.
* Prepare one stable idempotency key for this intended change when the tool requires it.

## Confirm the change

1. Approve the exact previewed plan.
2. Keep the semantic request unchanged.
3. Set `dry_run` to `false` when the tool uses that field.
4. Include the stable idempotency key.
5. Copy the preview's `confirm` value unchanged.
6. Submit the request once.
7. Read the returned result or operation ID.

The confirmation is bound to the action, target, user, selected account, authorization grant, and request digest. It is valid for 15 minutes and can be used only once.

## Expected result

Podigee accepts the exact previewed change. A direct operation returns its result. A long-running workflow returns an operation ID for monitoring.

## If confirmation is rejected

The confirmation can be expired, already used, changed in transit, or bound to an old authorization. Repeat the same request with `dry_run: true`, review the new preview, and submit the new confirmation unchanged.

Do not reuse the old confirmation. Reauthorization always requires a new preview.

## If the request changed

Do not apply the old confirmation. Request a new preview for the changed intent. Use a new idempotency key when the changed request represents a genuinely new user decision.

## 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/make-changes-safely/confirm-a-consequential-change.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.