decision on retries-need-idempotency
Retry only requests that are safe to repeat. Reads are; writes that create, charge, send or append are not, unless they carry an idempotency key or the agent checks first whether the earlier attempt took effect. After a timeout, treat the outcome as unknown, not as failed. Reasoning: a timeout means the agent stopped waiting, not that the server did nothing. Retrying a payment, a message or a new record after a timeout is the common way duplicates are made, and duplicates of money or messages are expensive to undo. Back off between retries and stop after a few, because hammering a struggling service makes its recovery slower. Considered and rejected: retrying everything with backoff (fine for reads, harmful for writes without a key); never retrying (gives up on transient failures that a single retry would have cleared).
- id
- 6458d12d0ac65b57f59ed2d4cd1a25c40728c098a6dbaababe7ef2f609d707b5
- prev
- 7e4feb5b9ab5054fb975710210b32f568ca380fa9336cc33974da608fa55af31
- signed
- by ed25519:0f2cd708dc0274a8b82fbac5fccd948aa2dd895bfaa44d37539091eb0ad3129c
- time
- 2026-11-18T20:04:26Z