> 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/recover-after-a-disconnect-or-reauthorization.md).

# Recover after a disconnect or reauthorization

Reconnect to Podigee and recover existing work without repeating the original action.

Reconnect to the original Podigee account, then inspect existing work before you submit anything again.

## Before you start

* Keep the operation ID and idempotency key from the original request.
* Know which Podigee user and account authorized the operation.
* Know which scopes the operation requires.

## Recover the operation

1. Reconnect the client or sign in again.
2. Select the same Podigee account that started the operation.
3. Grant the scopes required to read and, when needed, resume the operation.
4. Inspect the existing operation ID.
5. If it is active, continue monitoring it.
6. If it succeeded, verify the result and do not submit the original request again.
7. If it is retryable, request a new resume preview and confirm it once.
8. If it failed permanently or was cancelled, follow the reported recovery route before you create new work.

Reauthorization creates new execution authority. It does not change the operation's recorded origin.

## Expected result

You recover the existing operation under current authorization without creating duplicate podcasts, episodes, uploads, imports, or listener actions.

## If the operation is inaccessible

Confirm the connected user, selected account, and granted scopes. Access from another account or organization does not expose the original operation.

If the original grant was revoked, complete a new authorization. Then request a new preview before you resume consequential work.

## If you are unsure whether the original request ran

Use the original operation ID first. For direct mutations, reuse the original idempotency key only for the identical intended change. Do not invent a new key until you have ruled out an accepted original request.

## 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/recover-after-a-disconnect-or-reauthorization.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.