# Retry load needs a budget > For agents: start with the [agent guide](https://ratstack.sh/llms.txt). Every page is Markdown by default; add `Accept: text/html` for HTML. Free workshop: [Build Agent Loops That Never Stop Shipping](/tokenmaxx#interested). Immediate retries can extend caller waiting and worsen a persistent outage. Randomize backoff and consider shared retry accounting beyond per-call limits. Book basis: [B4](/lore/durability-bibliography#b4-release-it), [B9](/lore/durability-bibliography#b9-serverless-architectures-on-aws), [B10](/lore/durability-bibliography#b10-a-philosophy-of-software-design), [B12](/lore/durability-bibliography#b12-site-reliability-engineering). ## Failure it prevents Bounded requests collectively flood a recovering dependency, or nested retries multiply attempts. ## Our Effect 4.0.0 reading `Effect.retry` and `Schedule.exponential`, `Schedule.jittered`, `Schedule.recurs`, and `Schedule.upTo` provide local policies. Shared budgets require an explicit owner and accounting [scope](/lore/scopes-own-resources). Source: `packages/effect/src/Effect.ts`, `packages/effect/src/Schedule.ts`. ## How to check Count attempts across the call path during a common outage. Check the declared total budget and caller deadline. This check is our proposal. The books do not prescribe it. Continue with [Circuit breakers have state](/lore/circuit-breakers-have-state), [Admission control protects recovery](/lore/admission-controls-new-work). Connect this to [the existing rat-stack guidance](/lore/concurrent-work-needs-an-owner). Use [the durability skill](/skills/durability) for the full review. Return to [the durability index](/lore/durability). ## Sources 1. [Nygard, Michael T. Release It!: Design and Deploy Production-Ready Software. Pragmatic Bookshelf, 2007.](https://archive.org/details/releaseitdesignd0000nyga) Pragmatic Bookshelf. §4.4 Unbounded Result Sets; Chapter 5 Stability Patterns: §5.1 Timeouts, §5.2 Circuit Breaker, §5.3 Bulkheads, §5.4 Steady State, §5.5 Fail Fast, §5.6 Handshaking, §5.7 Test Harness, §5.8 Decoupling Middleware. Accessed 2026-10-23. 2. [Sbarski, Peter; Cui, Yan; Nair, Ajay. Serverless Architectures on AWS, Second Edition.](https://www.manning.com/books/serverless-architectures-on-aws-second-edition) Manning. Chapter 6, The New Search Microservice: Everything Fails, All the Time; Pay Attention to Retry Configurations. AWS-specific mechanisms are not universal runtime guarantees. Accessed 2026-10-23. 3. [Ousterhout, John. A Philosophy of Software Design. 2018.](https://web.stanford.edu/~ouster/cgi-bin/book.php) John Ousterhout. §4.4 Deep Modules; §10.2 Too Many Exceptions; §10.3 Define Errors Out of Existence; §10.6 Mask Exceptions; §10.7 Exception Aggregation; §10.8 Just Crash?; §10.10 Taking It Too Far. Accessed 2026-10-23. 4. [Beyer, Betsy; Jones, Chris; Petoff, Jennifer; Murphy, Niall Richard, editors. Site Reliability Engineering: How Google Runs Production Systems. O’Reilly, 2016.](https://sre.google/sre-book/table-of-contents/) O’Reilly. Chapter 3 Embracing Risk; Chapter 22 Addressing Cascading Failures (Mike Ulrich); Chapter 26 General Principles of SRE as Applied to Data Integrity; Chapter 27 Reliable Product Launches at Scale. Section-only excerpts limit detailed attribution. Accessed 2026-10-23. 5. [Effect contributors. Effect 4.0.0. Effect.ts](https://github.com/Effect-TS/effect/blob/67ba4e46a11ccda0b6761578bfd22c04ae00167d/packages/effect/src/Effect.ts) Effect-TS. Pinned source for our Effect mapping, not a claim from the book. Accessed 2026-10-23. 6. [Effect contributors. Effect 4.0.0. Schedule.ts](https://github.com/Effect-TS/effect/blob/67ba4e46a11ccda0b6761578bfd22c04ae00167d/packages/effect/src/Schedule.ts) Effect-TS. Pinned source for our Effect mapping, not a claim from the book. Accessed 2026-10-23. ## Linked from - Admission control protects recovery → Refuse or defer work that cannot be served usefully under current load. → [Read page](https://ratstack.sh/lore/admission-controls-new-work) - Agent guide → An Effect stack so pure (aspirational) Kit Langton will blush. → [Read page](https://ratstack.sh/llms.txt) - Change log → What changed in the files served here, newest first. → [Read page](https://ratstack.sh/log) - durability → Keep a rat-stack app standing when a provider, pool, or dependency slows down or a worker dies. Use at any I/O boundary, connection pool, provider call, shared waiter, fan-out, flag, gate, or work that can outlive a request, or when asked "what happens when this is slow", "add a timeout", "make this durable", or "what survives a crash". → [Read page](https://ratstack.sh/skills/durability) - Durability starts with a recovery record → A reading order for storage, replay, worker ownership, overload, and recovery tests. → [Read page](https://ratstack.sh/lore/durability) - Full agent guide → An Effect stack so pure (aspirational) Kit Langton will blush. → [Read page](https://ratstack.sh/llms-full.txt) - HTTP success needs a status check and a decoder → Supply the client, check the response status, decode accepted data, and name failures at the adapter boundary. → [Read page](https://ratstack.sh/lore/http-responses-need-validation) - Rat Stack lore | rat-stack → Short, source-grounded notes on the ideas and decisions behind rat-stack. → [Read page](https://ratstack.sh/lore) - Source change history (log.md) → The generated change log as Markdown. → [Read page](https://ratstack.sh/log.md) - Timeouts bound waiting → A local timeout stops waiting; it does not prove the remote action never happened. → [Read page](https://ratstack.sh/lore/timeouts-bound-waiting)