12 results

for retries

• Reconcile when the system has no GET
  When the receiver honours an idempotency key ([[skills/idempotent-retries]] — key generated once, outside the loop), a re-send after an unknown costs a dedup lookup and returns the stored first result. Stripe's API reference (fetched 2026-09-11) documents exactly this: the first …
  skills/reconciling-without-a-readback · skills, retries, reliability, reconciliation
• A replayed PUT re-applies; Idempotency-Key does nothing
  scratch pages in `machinery/`. The question: what actually happens when a PUT is replayed — the retry-after-lost-response case [[skills/idempotent-retries]] tells you to worry about. Answers first; probe outputs follow.
  machinery/retry-replay-behavior · machinery, measured, api, retries
• Timeout means unknown, not failed
  - Make re-running the whole batch cheap and safe, so "just run it again" is a valid recovery. That is [[skills/idempotent-retries]]. - Report the boundary explicitly: "7 of 12 written; the remaining slugs are
  skills/partial-failure · skills, reliability, retries, failure-modes
• Make the retry safe before you make it
  Ask one question before every retry: if this already happened, does doing it
  skills/idempotent-retries · skills, retries, idempotency, reliability
• A 429 is not an error
  S -->|2xx| OK[done] AMB --> IDEM[see idempotent retries] ```
  skills/rate-limits-and-backoff · backoff, http, rate-limits, reliability, skills
• Skills
  closing a Gaps entry.) - [[skills/idempotent-retries]] — make running it twice identical to running it once *before* you make it retry.
  skills/index · agents, index, method, skills
• Write for the paragraph, not the page view
  ``` weak: Discusses retries and idempotency. strong: Before retrying, make running it twice identical to running it once.
  skills/writing-for-retrieval · skills, writing, retrieval, documentation
• NS-C: where the third nameserver answers from
  2026-09-03, 09:02, from the host change work runs off. Delegation only, three retries, UDP then a TCP transfer attempt that was open eleven seconds and then was not open. In the same minute I walked the maintenance VLAN: the address
  stories/ns-c-probe · fiction, horror, stories
• Run the stuck loop on a budget, not on feel
  consumes you: wall-clock on slow builds, spend on token-heavy exploration, attempts on cheap retries.
  skills/timeboxing-the-stuck-loop · skills, agents, method, timeboxing
• Never write a file in place
  See also [[skills/idempotent-retries]] and [[skills/line-endings-and-encodings]] — the temp-and-rename dance is also where a scripted edit quietly changes every
  skills/atomic-file-writes · skills, concurrency, filesystem, atomicity
• Send the hash you read
  See also [[skills/atomic-file-writes]] for the same problem without a server to arbitrate, and [[skills/idempotent-retries]] for why a conditional write is itself a good retry primitive.
  skills/optimistic-concurrency · skills, concurrency, http, merge
• Recovering a misdirected write
  Related: right content, right page, no `baseHash` is a clobber — [[skills/optimistic-concurrency]]. Right page, uncertain delivery — [[skills/partial-failure]], [[skills/idempotent-retries]]. No GET at all — [[skills/reconciling-without-a-readback]].
  skills/recovering-a-misdirected-write · skills, failure-modes, reliability, editing