# Recover a connection

Resume a failed or waiting connection using its current state and the live help page.

Start with the affected source. A failed connection does not require resetting the installation, replacing the Vault, or reconnecting healthy apps.

## Open the current recovery page

```sh
indra --root "/absolute/path/to/your/Vault" recover
```

Keep this terminal running and open the returned live URL. `recover` opens assistance without starting another automatic connection pass. `help` is also available to review all source states.

With an active MCP agent, call `indra.action`:

```json
{"name":"connector.recover","params":{}}
```

Use the returned `recovery.url` while that MCP host remains alive. If all connections are already ready, the result may contain the readiness report without a new URL.

## Choose the next action from the state

| What you observe | Next step |
| --- | --- |
| Connected, but not checked | Choose **Check again** and inspect the result. |
| A successful empty read | Continue the task with that empty result; check filters or scope if surprising. |
| **Continue current authorization** | Reopen or continue the same live provider transaction. |
| QR code or device challenge | Complete that exact provider challenge on the required device. |
| Saved access could not be verified | Try **Check again** or supported **Reconnect with saved access**; inspect the account binding if failure persists. |
| Explicit authorization failure | Read the reason; use **Authorize again** when a fresh provider grant is needed. |
| Settings saved, connection unverified | Follow the displayed reload or setup instruction, then check again. |
| Missing local service, helper, or OS permission | Repair that stated prerequisite before retrying sign-in. |
| Help ended or link expired | Open a new help session; do not reuse the expired URL. |

An error code such as `failed_precondition` identifies a failed prerequisite, not its cause. Avoid assuming every such error means the password is wrong.

## Follow a connection job

A direct connection call can return a job:

```json
{
  "name": "connector.connect",
  "params": {
    "source": "gmail",
    "requestId": "gmail-recovery-1"
  }
}
```

Pass this to `indra.action`, then poll the returned ID:

```json
{"name":"connector.job","params":{"id":"<returned-job-id>"}}
```

The CLI equivalent is `action --json '<object>'` with the same Vault. Retain the job identity; a caller's wait ending does not prove the resident stopped.

If the job returns `browserContinuation`, an agent should inspect `browser-use` Actions and call `browser.observe` with the returned `sessionId`. Continue from that snapshot and keep checking the authorization job. Only provider verification establishes connection success. See [Sign-in and recovery](/docs/vision/browser-computer/sign-in-and-recovery).

If you are working without an agent and the automatic continuation provides no usable provider link, cancel the existing connection through its owner and confirm it ended. Then use the supported visible route, for example `connect --source gmail --presentation open`, with the same Vault. Do not run a competing manual sign-in while the old one is active.

## Cancel deliberately

Choose **Cancel connection** for the active help-page attempt. Do not treat a closed browser tab, lost response, or absent handle as a confirmed cancellation. A result can report pending cleanup; preserve that state before starting competing work.

**Continue later** ends the help session and keeps completed connections. Reopen help when you are ready. There is no universal cancellation Action for every provider operation.

## Return to the original task

After recovery, inspect onboarding or source status, then retry the small read or action that the task actually needs. Verify its result before saying the task is complete. If the prior operation may have changed external data before failing, inspect that object first to avoid a duplicate write.
