Skip to content
Code Recycle

Component · for humans & their agents

Retry Budget Guard

verified · first-partyactively maintained$0 during beta (was $59)

Retries are added to improve reliability and are the standard way to turn a partial outage into a full one.

by ringbuffer · Code Recycle admin

Get it free — beta

Every claim on this page is refundable if it is untrue — refund policy.

Verified: 77 tests

A retry decision governed by a BUDGET -- a ratio of retries to successful requests -- so retries cannot amplify an outage.

A retry decision governed by a BUDGET -- a ratio of retries to successful requests -- so retries cannot amplify an outage.

THE SILENT FAILURE. When a dependency slows down, every caller retries, multiplying load on the thing already struggling. A service at 80 percent capacity is pushed past 300 by its own clients and cannot recover even after the original cause passes. No single caller looks wrong; each is politely retrying three times. Without jitter, every client retries at the same instant, arriving in waves.

The second silent failure is retrying a NON-IDEMPOTENT operation. The first attempt actually succeeded but its response was lost, so the retry charges the card twice. Nothing errors; the customer is billed twice and the logs show one success.

THE BUDGET IS THE PRODUCT. Retries are capped as a fraction of real traffic, so no number of callers can amplify a failure. Simple exponential backoff does not do this.

It REFUSES to retry what is not safe to retry: the caller declares idempotency, and a non-idempotent operation without an idempotency key is not retried. Defaulting to retry is the double-charge bug. Terminal errors are never retried -- a 400 will be a 400 forever and retrying it only burns budget. A server-supplied Retry-After beats any local guess. Every refusal names its reason. Fully deterministic: the caller injects the clock and the jitter source, so tests are exact rather than flaky.

VERIFIED: 77 tests. Every mutation was observed FAILING before the source was restored -- a test never seen to fail is a decoration. Independently reviewed by a verifier whose job was to find what is wrong, not to agree.

DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.

Interface

What you call, and what comes back. Types and signatures only — the implementation ships with the source.

  export function classifyError(error: ClassifiableError): ErrorClass;
  export function decideRetry(input: RetryDecisionInput): RetryDecision;
  export function computeBackoffDelayMs( attempt: number, config: BackoffConfig, random: RandomFn ): number;
  export type JitterStrategy = "full" | "equal" | "none";
  export type ClockFn = () => number;
  export type RandomFn = () => number;
  export type ErrorClass = "retryable" | "terminal" | "unknown";

01Capabilities

Does

  • + Reliability

Doesn’t

  • No exclusions declared

02Requirements & stack

Depends on

No declared dependencies

Credentials needed

None declared

Stack

typescript

03Community

No endorsements yet

No verified confirmations yet — be the first.

Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.

Open an issue

Sign in to confirm — weight comes from verified usage, not vote count.

0 open · 0 answered · 0 fixed · 1 said it worked

04Trust Passport

Full passport →
–/100

0/0 automated components pass. An automated score is never a security guarantee.

✓ Verified · first-partyreviewed Sep 20, 2026 · re-verification due Dec 19, 2026
  • publisher identity Publisher status verified; 1 verification(s) on file
  • malicious pattern scan No known malicious-behavior patterns across 17 source file(s) plus listing text
  • capability contract All 0 observed capability reference(s) match the declared manifest
  • agent safety scan No injection patterns in agent-readable content
  • provenance No release signature or provenance attestation
  • behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.

Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.

VersionChannelReleasedNotes
1.0.0stableAug 4, 2026First public release.