Some Indra connection and sync operations continue after a caller stops waiting. The agent's overall task and an Indra background job have different lifetimes.
Use the identity returned by the operation to inspect it. A timeout does not establish that it failed, and starting a duplicate operation is not a status check.
Find the right status
Use your existing Vault path as $indra_root; see CLI commands.
| Question | Command | What it tells you |
|---|---|---|
| Which sources are usable now? | indra --root "$indra_root" manage --json '{"what":"sources"}' |
Current source state and configuration requirements. |
| What connection work remains? | indra --root "$indra_root" manage --json '{"what":"onboarding"}' |
Current readiness and operation evidence. |
| What happened in the latest automatic setup attempt? | indra --root "$indra_root" manage --json '{"what":"startup"}' |
That attempt's receipt; it is not a list of every previously connected source. |
| What runtime work is reported? | indra --root "$indra_root" manage --json '{"what":"status"}' |
Source state and available sync, fleet, and active-process information. |
These commands inspect Indra runtime work. They are not a universal inbox of every task in your agent's conversations.
Follow a connection job
Keep the actual job ID from connector.connect or its CLI output. Inspect the same job:
indra --root "$indra_root" action --json '{"name":"connector.job","params":{"id":"<returned-job-id>"}}'
The agent equivalent is:
indra.action({"name":"connector.job","params":{"id":"<returned-job-id>"}})
Read the state and any returned continuation. A waiting-user state can include a browser step that the host agent can still complete. If browserContinuation is present, use its existing session and current controls as described in Sign-in and recovery.
When the job reports a connected result, inspect source readiness and perform the small operation required by the original task. An available catalog and an exercised operation are different evidence.
For a known startup fleet request, fleet.receipt reads its existing receipt:
indra --root "$indra_root" action --json '{"name":"fleet.receipt","params":{"requestId":"<returned-requestId>"}}'
Use an ID you actually received. Indra's background host starts automatic setup; fleet.run is not an available interactive command.
Continue partial work
A supported sync can return complete: false with progress retained for continuation. Follow Sync information to continue that source's saved cursor. Keep the account binding and any returned backoff or reconnect requirement.
For browser.run_goal, a result with continuation.actor: "agent" retains a live session for the host agent. Continue its remaining page actions and verify the result. Do not start the same goal in a second session merely because embedded execution did not finish.
While waiting, inspect the existing operation when its state can usefully change. Follow returned retry information. Repeated immediate polls and repeated “still running” messages add no evidence.
Stop work or return later
There is no universal Indra job.cancel action or generic pause/resume control. Use the control belonging to the work:
| Work | Available control | What to check afterward |
|---|---|---|
| Active connection in Local connection help | Cancel connection. | The connection transaction's resulting state. |
| Current help page | Continue later or Done, as shown. | The page closes; completed connections remain. |
| Task-owned browser session | browser.close with its ID. |
cleanup: "confirmed". |
| Host agent's conversation/task | The host's own stop control or a direct stop instruction. | Whether any separate Indra/provider operation is still active. |
Ctrl+C stops the terminal command's wait. The connection CLI can attempt cancellation of its active authorization transaction, but do not treat a stopped process as proof that every operation or cleanup completed. Inspect the job or help page.
Stopping a wait does not roll back a completed provider change. If a write's outcome is unknown, inspect the destination before retrying or reporting cancellation.
Leave a useful handoff
If work remains ongoing, record its source, exact job or session ID, observed state, and next useful check. State what is verified and what remains pending. Keep expired sign-in links and credentials out of ordinary notes.
After the prerequisite finishes, return to the requested outcome. A successful sync is not yet the user's research answer. Continue work provides a handoff template.