Reconcile an unknown agent action
An operator runbook for ambiguous refunds, file changes and email sends, with provider evidence and safe escalation.
When an action outcome is unknown, stop creating new attempts for the same business operation. Preserve its identity, inspect the existing effect and look for evidence at the provider. An error message alone cannot establish whether a refund, email or file update happened.
Anlyon does not automatically resend an unknown action invocation. Supported reconciliation reads provider state. Unknown exposure remains held until the outcome is settled. A bounded search that returns nothing is not proof of absence.
Collect the incident record
Record the invocation and effect IDs, environment, action version, business operation key, target, amount and timestamps. Capture any provider identifier returned before the connection failed. Keep secret values and unnecessary customer content out of the incident notes.
| Action | Evidence to seek |
|---|---|
| Stripe refund | Refund record linked by ID or effect metadata |
| GitHub file update | Commit carrying the effect trailer |
| Resend email | Email record linked by ID or effect tag |
| Declared HTTP action | A match against its configured read-back rule |
Matching a file's current text is insufficient attribution: another actor could have written it. A customer saying they received no email also does not prove the send never happened.
Choose the recovery path
Read the effect's reconciliation history. If provider evidence establishes completion, use the supported settlement path. If no evidence is found, retain uncertainty. Anlyon's reconciliation is bounded; exhausted attempts require operator attention rather than an assumption of failure.
Some adapters support an explicit same-key replay within their documented provider window. That is different from starting a new invocation under a new key. Declared actions do not support a write replay. Follow the adapter reference before using any replay operation.
Close with an attributable decision
Where an operator resolves the outcome, attach the evidence and rationale. Manual resolution remains manual and must not be presented as provider verification. Tell the application which business operation was settled so a restarted agent does not recreate it.
Use the recovery reference, manual resolution and held allowance accounting. For a harmless reproduction of the failure, run the lost-response model.