> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usealmanac.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This handbook preview targets personal CLI 0.11.1. Check installed command help and the matching backend schema before using examples with another release. Examples with named people and placeholder IDs are fictional.

# External actions and uncertain results

> Use saved action receipts and the original service to resolve provider writes.

A provider write can succeed even when the caller loses its response. This matters for sending a draft, changing a calendar event, or running another provider tool: a second write with a new key could repeat the effect. Keep the intended account, tool or owned operation, exact input, and request key together before making the call. A command's successful exit only says the command returned; inspect the mutation or saved action status for its outcome.

```sh theme={"theme":{"light":"github-light","dark":"vesper"}}
almanac tools action --request-key meridian-send-1
almanac tools action ACTION_ID
```

This lookup reads Almanac's saved action ledger without contacting the provider. It also works for owned `email drafts create/delete/send` and `calendar create/update/delete`, which share that ledger with `tools run` writes. The receipt may say `requested`, `succeeded`, `failed`, or `unknown`. `unknown` means the effect cannot be established from the receipt; it does not mean failure. A missing response or null returned object reference does not establish that nothing happened.

After an uncertain result, read the receipt, then inspect the current original when an appropriate read exists. For a draft send, check the draft/thread or sent state with the same account; for a calendar change, read the exact calendar interval and event. Interpret both together, including incomplete pages or bodies. If the effect remains uncertain, report that uncertainty rather than silently issuing another send or booking. An identical request key is reserved for an identical retry of the same operation, account, and input; changing any of those requires a new decision, not reuse of the old key. A saved success can replay its result. An unfinished or unknown action is not automatically resent.

Generic provider writes use `almanac tools run TOOL --account ACCOUNT_ID --input @input.json --request-key KEY`. There is no confirmation flag or approval step: running the command performs the write, so direct user authorization and the active agent instructions govern whether it should happen. Without `--request-key`, the envelope reports the key the CLI chose; keep it for an identical retry. Revisioned [Almanac knowledge and work edits](/guides/edit-knowledge) have their own read/`--expect` recovery contract; `tools action` is for provider effects.