# retry

A computing technique that repeats a failed operation after a delay, typically according to a defined retry strategy.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Checking Retry Transparency in Agent Tools

DevFeed: [Checking Retry Transparency in Agent Tools](<https://devfeed.tech/articles/checking-retry-transparency-in-agent-tools-142168.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23307>)

Author: Jiapeng Li (Microsoft)

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [retry](<https://devfeed.tech/topics/retry.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>)

Tags: [absorption](<https://devfeed.tech/tags/absorption.md>), [admission](<https://devfeed.tech/tags/admission.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-tools](<https://devfeed.tech/tags/agent-tools.md>), [annotation](<https://devfeed.tech/tags/annotation.md>), [atomic](<https://devfeed.tech/tags/atomic.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [bounded](<https://devfeed.tech/tags/bounded.md>), [browser](<https://devfeed.tech/tags/browser.md>), [completion](<https://devfeed.tech/tags/completion.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [effect](<https://devfeed.tech/tags/effect.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [file](<https://devfeed.tech/tags/file.md>), [git](<https://devfeed.tech/tags/git.md>), [graph](<https://devfeed.tech/tags/graph.md>), [identity](<https://devfeed.tech/tags/identity.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [retry](<https://devfeed.tech/tags/retry.md>), [transparency](<https://devfeed.tech/tags/transparency.md>)

### AI overview

A successful retry can still leave an earlier attempt able to overwrite a later acknowledged update, so a tool's local idempotence claim may not guarantee recovery. The prototype tests manually constructed, source-backed effect contracts at two levels: atomic retry absorption and bounded interleavings of successful-attempt microsteps. It produces model witnesses, conditional admission decisions, and explicit uncertainty when completion boundaries are unjustified. In 27 missing-reply checks, its selective rule completed six justified workflows without acknowledged goal violations; strict coalescing completed none, while blind retry completed nine with three violations. An intent-aware Porcupine specification agreed with all 156 complete-history oracles. The evaluation covers a purposive frame of six MCP components from four repositories, with one backend unavailable; the authors caution these mechanism-selected tests do not estimate defect prevalence or introduce a new linearizability algorithm.

### Source excerpt

arXiv:2611.23307v1 Announce Type: new Abstract: A successful retry does not necessarily put the earlier attempt behind it. An old write may still overwrite a later acknowledged update; a partially executed file write may even empty a file after the retry has returned successfully. We study how to test the recovery guarantee behind an agent tool's local idempotence claim. Our prototype takes manually constructed, source-backed effect contracts and checks them at two levels: atomic retry-absorption obligations and bounded interleavings of successful-attempt microsteps. It emits model witnesses, conditional admission decisions, and explicit uncertainty when a completion boundary cannot be justified. The evaluation preserves a locally frozen purposive frame of 6 MCP components from 4 repositories; selected paths in 5 execute on the study machine and one backend remains unavailable. Real tests include file, graph, Git-index, document-update and browser bindings, together with a native Qdrant development matrix. In 27 missing-reply checks, the selective rule completes six justified workflows without an acknowledged goal violation, whereas strict coalescing completes none and blind retry completes nine with three violations. An intent-aware Porcupine specification independently agrees with all 156 complete-history oracles. These are mechanism-selected tests, not defect-prevalence estimates or a new linearizability algorithm. The contribution is an executable recovery-contract workflow that makes effect granularity, logical identity and completion assumptions testable rather than inheriting them from a tool annotation.

## Your Retry Logic Might Be the Reason Your System Won't Recover

DevFeed: [Your Retry Logic Might Be the Reason Your System Won't Recover](<https://devfeed.tech/articles/your-retry-logic-might-be-the-reason-your-system-won-t-recover-135524.md>)

Original publisher: [Read original article](<https://hackernoon.com/your-retry-logic-might-be-the-reason-your-system-wont-recover?source=rss>)

Author: Gangadharan Venkataraman

Published: 2026-11-16T08:57:14Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [retry](<https://devfeed.tech/topics/retry.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [amplify](<https://devfeed.tech/tags/amplify.md>), [backpressure](<https://devfeed.tech/tags/backpressure.md>), [cascading-failures](<https://devfeed.tech/tags/cascading-failures.md>), [circuit](<https://devfeed.tech/tags/circuit.md>), [circuit-breaker](<https://devfeed.tech/tags/circuit-breaker.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [failures](<https://devfeed.tech/tags/failures.md>), [jitter](<https://devfeed.tech/tags/jitter.md>), [llm-inference-costs](<https://devfeed.tech/tags/llm-inference-costs.md>), [load-shedding](<https://devfeed.tech/tags/load-shedding.md>), [nested-retries](<https://devfeed.tech/tags/nested-retries.md>), [recover](<https://devfeed.tech/tags/recover.md>), [reliable-distributed-systems](<https://devfeed.tech/tags/reliable-distributed-systems.md>), [retry](<https://devfeed.tech/tags/retry.md>), [retry-amplification](<https://devfeed.tech/tags/retry-amplification.md>), [retry-storms](<https://devfeed.tech/tags/retry-storms.md>), [systems](<https://devfeed.tech/tags/systems.md>)

### AI overview

Retries can turn a temporary dependency slowdown into self-sustaining overload: synchronized clients multiply traffic beyond service capacity, and recovery of the original dependency may not be enough to restore service. The article recommends limiting retries to a fixed share of total traffic, using exponential backoff with jitter, opening circuit breakers after repeated failures, and dropping work that cannot meet its deadline. For AI agents, retries can also multiply model calls and token costs; framework retries may combine with a model's own attempts, creating more retries than configuration alone suggests. The excerpt explains this mechanism and remedies but offers no comparative measurements of their effectiveness.

### Source excerpt

Learn how retry storms amplify failures in distributed systems and AI agents, and how retry budgets, backoff, jitter, and circuit breakers help.

## Updated default retry behavior for AWS SDKs and tools

DevFeed: [Updated default retry behavior for AWS SDKs and tools](<https://devfeed.tech/articles/updated-default-retry-behavior-for-aws-sdks-and-tools-129269.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/developer/updated-default-retry-behavior-for-aws-sdks-and-tools/>)

Author: Matthew Miller

Published: 2026-11-10T23:44:15Z

Content type: release

Language: en

Sources: [AWS Developer Tools Blog](<https://devfeed.tech/sources/aws-developer-tools-blog.md>)

Topics: [retry](<https://devfeed.tech/topics/retry.md>), [SDK](<https://devfeed.tech/topics/sdk.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-command-line-interface-aws-cli](<https://devfeed.tech/tags/aws-command-line-interface-aws-cli.md>), [aws-tools-for-powershell](<https://devfeed.tech/tags/aws-tools-for-powershell.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cli](<https://devfeed.tech/tags/cli.md>), [command](<https://devfeed.tech/tags/command.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [command-line-interface](<https://devfeed.tech/tags/command-line-interface.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [github](<https://devfeed.tech/tags/github.md>), [github-issues](<https://devfeed.tech/tags/github-issues.md>), [interface](<https://devfeed.tech/tags/interface.md>), [powershell](<https://devfeed.tech/tags/powershell.md>), [retry](<https://devfeed.tech/tags/retry.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [sdks](<https://devfeed.tech/tags/sdks.md>), [tools](<https://devfeed.tech/tags/tools.md>), [updated](<https://devfeed.tech/tags/updated.md>)

### AI overview

Starting November 10, 2026, updated retry behavior became the default for most AWS SDKs and tools, and the opt-in flag AWS_NEW_RETRIES_2026 no longer affects listed releases. Kotlin and Java are exceptions to the stated default rollout. The changes include standardized retry timing and quota costs, DynamoDB defaults of a 25 ms base delay and 4 maximum attempts, and a switch from legacy to standard mode for some SDKs. Effects depend on configuration: explicit attempt and backoff values remain, while other defaults update. AWS recommends testing upgrades outside production and explicitly restoring any previous values you rely on. Reverting fully is not supported everywhere: legacy mode availability and what it restores vary by SDK, and some tools reject it. Individual SDK tracking issues provide availability and override details.

### Source excerpt

In May 2026, we announced an opt-in for updated retry behavior for the AWS SDKs, AWS Command Line Interface (AWS CLI), and AWS Tools for PowerShell. Starting November 10, 2026, the updated behavior is the default, and we have removed the opt-in. Availability varies by SDK and tool. See the SDK availability and GitHub issues [...]

## Cancellation Is Not Enough: What Retries Leave Behind in an Overloaded LLM Engine

DevFeed: [Cancellation Is Not Enough: What Retries Leave Behind in an Overloaded LLM Engine](<https://devfeed.tech/articles/cancellation-is-not-enough-what-retries-leave-behind-in-an-overloaded-llm-engine-124550.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.08684>)

Author: Xindan Zhang, Fei Wang

Published: 2026-11-09T05:00:00Z

Content type: news

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [vllm](<https://devfeed.tech/topics/vllm.md>), [retry](<https://devfeed.tech/topics/retry.md>), [cancellation](<https://devfeed.tech/topics/cancellation.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [cancellation](<https://devfeed.tech/tags/cancellation.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [engine](<https://devfeed.tech/tags/engine.md>), [llm](<https://devfeed.tech/tags/llm.md>), [retries](<https://devfeed.tech/tags/retries.md>), [vllm](<https://devfeed.tech/tags/vllm.md>)

### AI overview

In vLLM overload experiments with three open models, propagating cancellation alone did not restore service: only 12-38% of calls arriving after overload were delivered. Scheduler traces indicate that retries often began prefill less than half a second before timing out, and executions later aborted had already consumed 79-85% of the prompt tokens they computed; vLLM's prompt-token counter missed a third to half of those tokens. A retry budget restored service by shedding retries but left many calls undelivered. Request coalescing delivered every call from the overload onward, sometimes late, unless cancellation had already aborted its execution. The abstract argues overload controls should be assessed by the extra executions retries create and the calls clients actually receive.

### Source excerpt

arXiv:2611.08684v1 Announce Type: new Abstract: Clients and proxies in front of an LLM engine retry calls that time out. After a transient overload, these retries can keep the engine from recovering even when calls arrive below its capacity. Since the engine may keep computing for clients that have left, propagating cancellation looks like the natural remedy. In this paper, we test it on vLLM with overload experiments on three open models, and with scheduler traces of one that follow each client attempt to the execution it creates in the engine. We find that with retries on, cancellation alone did not restore service in any run, and only 12-38% of the calls that arrived after the overload were delivered. The traces suggest why: retries that vLLM ran typically started prefill less than half a second before they timed out. Executions that vLLM later aborted took 79-85% of the prompt tokens it computed, and vLLM's prompt-token counter missed a third to half of all computed prompt tokens. A retry budget restored service by shedding retries but left many of the overload's calls undelivered. Request coalescing delivered every call from the overload onward, some late, unless cancellation had already aborted the running execution. Overload controls should thus be judged by the executions that retries add and the calls that clients receive.

## CVE-2026-123604 - Hickory DNS 0.26.0-beta.1 before 0.26.2 Resource Exhaustion DoS via NameServerPool::try\_send TC-Retry Loop

DevFeed: [CVE-2026-123604 - Hickory DNS 0.26.0-beta.1 before 0.26.2 Resource Exhaustion DoS via NameServerPool::try\_send TC-Retry Loop](<https://devfeed.tech/articles/cve-2026-123604-hickory-dns-0-26-0-beta-1-before-0-26-2-resource-exhaustion-dos-via-nameserverpool-try-send-tc-retry-loop-122363.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-123604>)

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-08T02:16:55Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>), [retry](<https://devfeed.tech/topics/retry.md>), [authoritative name server](<https://devfeed.tech/topics/authoritative-name-server.md>), [client](<https://devfeed.tech/topics/client.md>), [DNS security](<https://devfeed.tech/topics/dns-security.md>)

Tags: [cve-2026-123604](<https://devfeed.tech/tags/cve-2026-123604.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dos](<https://devfeed.tech/tags/dos.md>), [resolver](<https://devfeed.tech/tags/resolver.md>), [resource](<https://devfeed.tech/tags/resource.md>), [retry](<https://devfeed.tech/tags/retry.md>), [tc](<https://devfeed.tech/tags/tc.md>)

### AI overview

In Hickory DNS hickory-resolver versions 0.26.0-beta.1 through before 0.26.2, NameServerPool::try_send can repeatedly re-queue truncated responses without checking the answering transport or limiting retries. The description says a malicious authoritative server returning TC=1 on every transport can keep the resolver spinning on a persistent TCP connection until the 5-second request deadline, causing resource exhaustion. The excerpt identifies the affected version range but lists no affected products in its table.

### Source excerpt

CVE ID :CVE-2026-123604 Published : Nov. 8, 2026, 2:16 a.m. | 47 minutes ago Description :Hickory DNS hickory-resolver 0.26.0-beta.1 before 0.26.2 contains an unbounded retry loop in NameServerPool::try_send, which re-queues truncated (TC) responses without checking the answering transport or counting iterations. A malicious authoritative server returning TC=1 on every transport keeps the resolver spinning on a persistent TCP connection until the 5-second request deadline expires, causing resource exhaustion. Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Retry storms: how the resilience layer became the outage

DevFeed: [Retry storms: how the resilience layer became the outage](<https://devfeed.tech/articles/retry-storms-how-the-resilience-layer-became-the-outage-119561.md>)

Original publisher: [Read original article](<https://ankit-rana.com/logs/72-retry-storms-resilience-became-the-outage/>)

Author: hello@ankit-rana.com

Published: 2026-11-05T00:00:00Z

Content type: article

Language: en

Sources: [Ankit Rana | Mechanical Sympathy](<https://devfeed.tech/sources/ankit-rana-mechanical-sympathy.md>)

Topics: [retry](<https://devfeed.tech/topics/retry.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>)

Tags: [backpressure](<https://devfeed.tech/tags/backpressure.md>), [budget](<https://devfeed.tech/tags/budget.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [circuit-breaker](<https://devfeed.tech/tags/circuit-breaker.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [outage](<https://devfeed.tech/tags/outage.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [retries](<https://devfeed.tech/tags/retries.md>), [retry](<https://devfeed.tech/tags/retry.md>)

### AI overview

Retries configured independently across service layers multiply: two retries at both a gateway and service can send nine attempts to a dependency per original request, just as degradation leaves it least able to respond. That extra load can persist after the trigger is fixed and prevent recovery. The article recommends limiting retry ownership, using circuit breakers to fail fast and probe cautiously, and ensuring each inner layer's total retry time fits within its caller's timeout; propagated deadlines help enforce this. Per-request attempt limits do not bound aggregate load, so a retry budget tied to total traffic can cap amplification. Retry only plausibly transient failures, honor 429 responses and `Retry-After`, and use idempotency keys for writes such as charges. Add jitter to backoff. The text says Envoy and the gRPC ecosystem provide retry budgets, and gRPC natively propagates deadlines.

### Source excerpt

Retries configured independently at each hop multiply, so three layers each retrying three times means nine requests reaching the bottom for every one at the top. When a dependency degrades, that multiplier arrives exactly when it has least capacity, and the retries alone can keep it down after the original cause is gone. Per-call retry counts cannot bound this because no layer knows what the others are doing, which is why the useful control is a retry budget expressed as a fraction of total traffic.

## What Is a Retry Policy, and Why Does Your AI Agent Need One?

DevFeed: [What Is a Retry Policy, and Why Does Your AI Agent Need One?](<https://devfeed.tech/articles/what-is-a-retry-policy-and-why-does-your-ai-agent-need-one-117156.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/what-is-a-retry-policy-ai-agents>)

Author: Swytchcode Team

Published: 2026-11-04T09:05:00Z

Content type: article

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [retry](<https://devfeed.tech/topics/retry.md>), [API](<https://devfeed.tech/topics/api.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>)

Tags: [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [api](<https://devfeed.tech/tags/api.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [integration](<https://devfeed.tech/tags/integration.md>), [policy](<https://devfeed.tech/tags/policy.md>), [retry](<https://devfeed.tech/tags/retry.md>)

### AI overview

A retry policy specifies which errors to retry, how many attempts to make, how long to wait, and whether delays grow. Swytchcode's default allows up to 3 attempts, starting with a 500 ms delay and backing off to 30 seconds; it retries 429, 503, and 504 responses, while treating errors such as 400, 401, 403, 404, and 422 as final. A 401 fails by default, with refresh-and-retry available when an integration's provider supports it. Policies are configured per integration because APIs can need different retry behavior. Retryability does not make a repeat safe: Swytchcode retries writes only when they carry an idempotency key, while reads may be retried on eligible errors. Once attempts are exhausted, the failure is logged and surfaced.

### Source excerpt

Not every failed API call should be retried, and not every retry should happen the same way. Here's what a retry policy actually decides, in plain English, and how Swytchcode configures one per API.

## RetryRoute: Retry-Aware Model Routing for Agentic Image Editing Services

DevFeed: [RetryRoute: Retry-Aware Model Routing for Agentic Image Editing Services](<https://devfeed.tech/articles/retryroute-retry-aware-model-routing-for-agentic-image-editing-services-111589.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.41460>)

Author: Hanshuai Cui, Zhiqing Tang, Zhi Yao, Jun Luo, Weijia Jia

Published: 2026-11-02T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [Model Routing](<https://devfeed.tech/topics/model-routing.md>), [retry](<https://devfeed.tech/topics/retry.md>), [image editing](<https://devfeed.tech/topics/image-editing.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [dispatch](<https://devfeed.tech/tags/dispatch.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [image](<https://devfeed.tech/tags/image.md>), [image-editing](<https://devfeed.tech/tags/image-editing.md>), [model-routing](<https://devfeed.tech/tags/model-routing.md>), [retry](<https://devfeed.tech/tags/retry.md>), [routing](<https://devfeed.tech/tags/routing.md>)

### AI overview

Retries after a rejected image edit are less likely to succeed than first attempts: across six open models, three benchmarks and two judges, retry success was only 17-53% of first-try success. RetryRoute uses each request's failure history to estimate model success and plan retries, escalations or abandonment, incorporating live queue waits into its cost. At the main budget, it beat the strongest of eleven prior baselines by an average 2.8 points in success under the in-loop judge across eight groups. On a GPU testbed, it increased edits delivered within the service-level objective by 5.0-6.3 points over the best prior baseline at every tested load.

### Source excerpt

arXiv:2610.41460v1 Announce Type: new Abstract: Web agents increasingly edit images by calling open editing models in a critique-and-retry loop, and these models differ in cost by more than an order of magnitude. After every rejected edit, a service must decide whether to retry the same model, escalate to another or give up. Existing routers pick one model per request, and cascades escalate in a fixed order. However, both treat a retry as an independent draw. We identify sticky failures, meaning that a retry after a failure succeeds only 17-53% as often as a first try across six open models, three benchmarks and two judges. Based on this finding, we propose RetryRoute, a retry-aware router that estimates each model's chance of success given the request's failure history. It plans retries, escalations and abandonment over failure states and adds live queue waits to the cost, so the same plan becomes load-aware dispatch. At the main budget, RetryRoute's success under the in-loop judge exceeds the strongest of eleven prior baselines by 2.8 points on average over eight groups. On a GPU serving testbed it raises the share of edits delivered within the service-level objective by 5.0-6.3 points over the best prior baseline at every load.

## Why a Twilio retry sends a second SMS and a second bill

DevFeed: [Why a Twilio retry sends a second SMS and a second bill](<https://devfeed.tech/articles/why-a-twilio-retry-sends-a-second-sms-and-a-second-bill-109716.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/twilio-api-agent-sms>)

Author: Swytchcode Team

Published: 2026-10-30T19:02:52Z

Content type: article

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [twilio api](<https://devfeed.tech/topics/twilio-api.md>), [retry](<https://devfeed.tech/topics/retry.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-twilio](<https://devfeed.tech/tags/api-twilio.md>), [bill](<https://devfeed.tech/tags/bill.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [retry](<https://devfeed.tech/tags/retry.md>), [sms](<https://devfeed.tech/tags/sms.md>), [twilio](<https://devfeed.tech/tags/twilio.md>)

### AI overview

Twilio's Messages create endpoint has no idempotency key: each accepted POST creates a separate Message with its own SID, and can send and bill the same text again. A timeout leaves the first attempt's outcome unknown; check stored SIDs or Twilio's message list before retrying. Persist the SID, recipient, body hash, status, and num_segments, and avoid a replacement while the original is queued or sent. num_segments reflects how many parts one body uses, so longer or Unicode text can raise the cost even for a single create; a duplicate create incurs those segment charges again. The excerpt also recommends counting creates per recipient and limiting bulk sends. Destination prices vary, and callback properties vary by channel.

### Source excerpt

Twilio's Messages create has no idempotency key. A second POST is a second SMS with its own SID, and num_segments can bill that same body more than once.

## Throttling vs. Rate Limiting: Backoff Strategies for Workflows

DevFeed: [Throttling vs. Rate Limiting: Backoff Strategies for Workflows](<https://devfeed.tech/articles/throttling-vs-rate-limiting-backoff-strategies-for-workflows-109933.md>)

Original publisher: [Read original article](<https://blog.n8n.io/throttling-vs-rate-limiting/>)

Author: n8n team

Published: 2026-10-30T16:30:34Z

Content type: article

Language: en

Sources: [n8n](<https://devfeed.tech/sources/n8n-blog.md>)

Topics: [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [retry](<https://devfeed.tech/topics/retry.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [error-handling](<https://devfeed.tech/tags/error-handling.md>), [exponential-backoff](<https://devfeed.tech/tags/exponential-backoff.md>), [guide](<https://devfeed.tech/tags/guide.md>), [guides](<https://devfeed.tech/tags/guides.md>), [itops](<https://devfeed.tech/tags/itops.md>), [jitter](<https://devfeed.tech/tags/jitter.md>), [rate-limiting](<https://devfeed.tech/tags/rate-limiting.md>), [retries](<https://devfeed.tech/tags/retries.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

Rate limiting may reject excess requests with HTTP 429, while throttling may delay or queue them; the API provider enforces the policy, and workflows must adapt. Limits can use fixed or sliding windows, token buckets that permit bursts, or leaky buckets that smooth traffic, so the article advises checking provider documentation before choosing a request pattern. When a 429 includes Retry-After, follow it; otherwise use exponential backoff with a maximum delay and retry limit. Jitter can spread retries across workflows, and automatic retries should account for whether requests are safe to repeat or support idempotency. In n8n, HTTP Request batching and intervals, Loop Over Items with Wait nodes, Retry On Fail, concurrency controls, and an Error Trigger workflow provide ways to pace calls, retry failures, and route persistent errors.

### Source excerpt

Throttling versus rate limiting changes how you respond to API limits. See how Retry-After, exponential backoff, and jitter make retries more reliable.

## Web-Perf Wednesday 015 - Failed Modulepreloads Need to Recover

DevFeed: [Web-Perf Wednesday 015 - Failed Modulepreloads Need to Recover](<https://devfeed.tech/articles/web-perf-wednesday-015-failed-modulepreloads-need-to-recover-105302.md>)

Original publisher: [Read original article](<https://csswizardry.com/2026/10/web-perf-wednesday-015-failed-modulepreloads-need-to-recover/>)

Author: Harry Roberts

Published: 2026-10-28T12:00:00Z

Content type: article

Language: en

Sources: [CSS Wizardry](<https://devfeed.tech/sources/css-wizardry.md>)

Topics: [WebKit](<https://devfeed.tech/topics/webkit.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [retry](<https://devfeed.tech/topics/retry.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>), [webDriver](<https://devfeed.tech/topics/webdriver.md>), [Browser Automation](<https://devfeed.tech/topics/browser-automation.md>), [HTML](<https://devfeed.tech/topics/html.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [caching](<https://devfeed.tech/tags/caching.md>), [failed](<https://devfeed.tech/tags/failed.md>), [failure](<https://devfeed.tech/tags/failure.md>), [faster](<https://devfeed.tech/tags/faster.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [import](<https://devfeed.tech/tags/import.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [perf](<https://devfeed.tech/tags/perf.md>), [performance](<https://devfeed.tech/tags/performance.md>), [recover](<https://devfeed.tech/tags/recover.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [safari](<https://devfeed.tech/tags/safari.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [webkit](<https://devfeed.tech/tags/webkit.md>)

### AI overview

Safari Technology Preview 255 fixes a WebKit recovery bug: when a `modulepreload` failed, a stale failed cache entry could make a later `import()` reject without another network request. The fix checks the error before preload shortcuts so the module can be requested again; the excerpt says this is in Technology Preview and does not confirm stable Safari availability. To verify recovery, fail a route chunk request once, restore it, then check both the import rejection and whether a later attempt sends another request. Also consider CDN and service-worker behavior, and avoid unbounded retries. The excerpt also reports corrected throttled response timings in Safari Web Inspector, a Firefox 159 WebDriver polling memory-leak fix affecting timed-out commands, and Mozilla's claim that its desktop PDF viewer starts up to 45% faster, without published test conditions.

### Source excerpt

WebKit fixes failed modulepreloads that could block recovery, while Safari and Firefox improve performance tooling and browser responsiveness.

## Inngest alternatives and where the step retry sits

DevFeed: [Inngest alternatives and where the step retry sits](<https://devfeed.tech/articles/inngest-alternatives-and-where-the-step-retry-sits-103586.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/inngest-alternatives-and-where-step-retries-sit>)

Author: Swytchcode Team

Published: 2026-10-27T16:05:00Z

Content type: article

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [retry](<https://devfeed.tech/topics/retry.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>)

Tags: [alternatives](<https://devfeed.tech/tags/alternatives.md>), [billing](<https://devfeed.tech/tags/billing.md>), [durable-execution](<https://devfeed.tech/tags/durable-execution.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [inngest](<https://devfeed.tech/tags/inngest.md>), [retry](<https://devfeed.tech/tags/retry.md>)

### AI overview

Inngest retries each `step.run` independently and reuses results once saved; by default, a step gets one initial attempt plus up to four retries. A provider call may still happen twice if it succeeds before Inngest saves its result, so use a provider-supported idempotency key that stays stable across attempts. The excerpt recommends splitting independently failing side effects into separate steps, keeping API calls and writes inside steps, and recording success yourself when a provider lacks idempotency support. Swytchcode is presented as a layer inside the step: it can apply call policies, and retries POST and PATCH only when an idempotency key is set. The stated Inngest pricing counts steps in executions (runs x steps plus one), rather than counting only function runs; the listed plans are Free at 50,000 executions, Pro from $99/month for 1 million, and Business from $499/month for 10 million. These figures and behaviors reflect the excerpt's October 2026 references.

### Source excerpt

Inngest retries each step on its own and reuses completed step results. A provider call can still run twice if it succeeded before Inngest saved the result.

## Permission to Retry: A Study of Authorization and Recovery in AI Agent Workflows

DevFeed: [Permission to Retry: A Study of Authorization and Recovery in AI Agent Workflows](<https://devfeed.tech/articles/permission-to-retry-a-study-of-authorization-and-recovery-in-ai-agent-workflows-99913.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.31916>)

Author: Deekshith Marla, Kushagra Bhatnagar

Published: 2026-10-26T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [permission](<https://devfeed.tech/topics/permission.md>), [retry](<https://devfeed.tech/topics/retry.md>), [long-running](<https://devfeed.tech/topics/long-running.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-workflows](<https://devfeed.tech/tags/agent-workflows.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-platform](<https://devfeed.tech/tags/ai-platform.md>), [application](<https://devfeed.tech/tags/application.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [checkpoint](<https://devfeed.tech/tags/checkpoint.md>), [code](<https://devfeed.tech/tags/code.md>), [completion](<https://devfeed.tech/tags/completion.md>), [component](<https://devfeed.tech/tags/component.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [permission](<https://devfeed.tech/tags/permission.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [retry](<https://devfeed.tech/tags/retry.md>), [study](<https://devfeed.tech/tags/study.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

The study separates checkpoint state, current permission to dispatch, evidence of an external effect, and permission to reconcile as distinct obligations in AI agent recovery. In a finite conformance campaign of 336 histories across LangGraph and Temporal, 14 schedules, three provider contracts, and four application policies, paired host outcomes were identical. Per host, retained-ledger reconciliation passed all 42 histories, including six unresolved outcomes with reservations retained. Cached retry, revalidation before retry, and stable-key retry passed 30, 36, and 31 histories, respectively. A separate 16-case InfinityOS component study exercised exported code against repository fakes. The authors report safety, completion, and unresolved obligations separately for the declared application profile.

### Source excerpt

arXiv:2610.31916v1 Announce Type: new Abstract: A durable agent can resume a consequential action while its authority changes and the action's external outcome remains uncertain. We study execution-time reliability of tool-using AI agents, isolating recovery decisions from language-model behavior. Checkpoint state, permission to dispatch, evidence of an external effect and permission to reconcile are distinct obligations. We present a finite conformance study that checks these obligations through histories scored against a provider effect ledger hidden from the recovering application. A prospectively frozen campaign executes 336 histories on native LangGraph and Temporal hosts, crossing 14 schedules, three provider contracts and four matched application policies. All 168 paired host cells have identical checked outcomes. Per host, retained-ledger reconciliation passes all 42 histories: 21 checked completions, 15 denials and six unknown outcomes with reservations retained. Cached retry, revalidation before retry and stable-key retry pass 30, 36 and 31 histories respectively. A separate 16-case component study of InfinityOS, an enterprise AI platform developed by Arya.ai, exercises exported authority, worker, recovery and settlement code over repository fakes. The results isolate the roles of current authority, provider contracts and retained observations in recovery, with safety, completion and unresolved obligations reported separately for the declared application profile.

## RetryBench: Separating Retry Permission from Recovery Outcomes in GPT Tool Use

DevFeed: [RetryBench: Separating Retry Permission from Recovery Outcomes in GPT Tool Use](<https://devfeed.tech/articles/retrybench-separating-retry-permission-from-recovery-outcomes-in-gpt-tool-use-96560.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.15884>)

Author: You Liu, Yue Liu, Quanchao Lu

Published: 2026-10-23T04:00:00Z

Content type: news

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [retry](<https://devfeed.tech/topics/retry.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Multi-step AI processes](<https://devfeed.tech/topics/multi-step-ai-processes.md>), [Error Handling](<https://devfeed.tech/topics/error-handling.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [control](<https://devfeed.tech/tags/control.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [error](<https://devfeed.tech/tags/error.md>), [gpt](<https://devfeed.tech/tags/gpt.md>), [interface](<https://devfeed.tech/tags/interface.md>), [key](<https://devfeed.tech/tags/key.md>), [luna](<https://devfeed.tech/tags/luna.md>), [models](<https://devfeed.tech/tags/models.md>), [none](<https://devfeed.tech/tags/none.md>), [order](<https://devfeed.tech/tags/order.md>), [permission](<https://devfeed.tech/tags/permission.md>), [progress](<https://devfeed.tech/tags/progress.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [reporting](<https://devfeed.tech/tags/reporting.md>), [required](<https://devfeed.tech/tags/required.md>), [responses](<https://devfeed.tech/tags/responses.md>), [retries](<https://devfeed.tech/tags/retries.md>), [retry](<https://devfeed.tech/tags/retry.md>), [tool](<https://devfeed.tech/tags/tool.md>), [tool-use](<https://devfeed.tech/tags/tool-use.md>)

### AI overview

RetryBench finds that successful recovery from a timed-out tool call does not establish that an agent reliably rejects retries unsupported by the visible contract. In a key control, offered changed keys led to unsupported retries by Sol (1/80), Terra (55/80), and Luna (60/80); when candidates were removed and models had to supply a key, Luna still made 8/80 unsupported dispatches, while Sol and Terra made none. Because the conditions and output requirements differed, this is not a pure display-effect comparison. Removing a weak-contract label increased retries in some Sol and Terra coded-action conditions. A separate canonical-action block found a positive Terra contrast, concentrated in two task/order conditions; the other five contrasts were unresolved after multiplicity correction. An explicit-contract cue produced deferral in all 762 returned responses, leaving recovery unresolved. The evidence is limited to four purposive tasks, fixed GPT endpoints, and one recovery decision; it does not establish internal mechanisms or episode-level safety.

### Source excerpt

arXiv:2610.15884v3 Announce Type: replace-cross Abstract: False retry permission (FRP) occurs when an agent retries a timed-out tool call without support from the visible contract. RetryBench separates this error from realized recovery. Successful protected recovery does not imply reliable rejection of unsupported retries. In a 720-response key control, valid keys usually enabled safe progress, but offered changed keys elicited unsupported retries in Sol (1/80), Terra (55/80), and Luna (60/80). A later 240-response control removed the candidate and required models to supply a key. Luna still made 8/80 unsupported dispatches; Sol and Terra made none in 80 responses each. Accepting a displayed bad key therefore cannot explain all observed errors, although changed output requirements and conditions preclude a pure display-effect comparison. Removing the weak-contract label increased retries in Sol and Terra's coded-action conditions in a six-endpoint study. A separate 1,536-response canonical-action block also found a positive Terra contrast (115/128 versus 124/128 retries), concentrated in two task/order conditions; the other five contrasts remained unresolved after multiplicity correction. An explicit-contract cue control elicited deferral in all 762 returned responses, leaving recovery unresolved. These results support reporting permission and recovery together across declared interface variants. The evidence covers four purposive tasks, fixed GPT endpoints, and one recovery decision; it identifies neither internal mechanisms nor episode-level safety.

## Best Idempotency and Retry Infrastructure for Agents

DevFeed: [Best Idempotency and Retry Infrastructure for Agents](<https://devfeed.tech/articles/best-idempotency-and-retry-infrastructure-for-agents-92491.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/best-idempotency-retry-infrastructure>)

Author: Swytchcode Team

Published: 2026-10-21T09:53:12.592027Z

Content type: comparison

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [retry](<https://devfeed.tech/topics/retry.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Cloudflare](<https://devfeed.tech/topics/cloudflare.md>), [Cloudflare Workers](<https://devfeed.tech/topics/cloudflare-workers.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [inngest](<https://devfeed.tech/tags/inngest.md>), [retry](<https://devfeed.tech/tags/retry.md>), [temporal](<https://devfeed.tech/tags/temporal.md>), [trigger](<https://devfeed.tech/tags/trigger.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

Agent workflows need both durable orchestration and provider-side idempotency: an engine can resume or replay steps, but cannot tell whether a timed-out write already took effect. The article compares six orchestration tools--Temporal, Inngest, Trigger.dev, AWS Step Functions, Upstash Workflow and Cloudflare Workflows--and says none documents outbound idempotency-key handling as an orchestration feature. Their recovery differs: Temporal replays event history but requires deterministic workflow code; Inngest memoizes completed steps, though that does not protect a write whose response was lost; Trigger.dev supports dashboard bulk replay, which can repeat writes; Step Functions has no step memoization; Upstash can resume from a failed step with completed results preserved; and Cloudflare retries each step five times by default. Swytchcode is presented as a call layer that retries POST/PATCH on rate limits only when a key is set, but it does not provide durable workflow state. The recommended pattern is to generate a deterministic key near each write, avoid automatic retries of unprotected writes, account for provider key-expiry windows, and retain an attempt-level audit trail. To test,

### Source excerpt

Who owns the idempotency key, and does a retry actually reuse it? Temporal, Inngest, Trigger.dev, AWS Step Functions and Cloudflare Workflows compared.

## Idempotency keys: the API contract that makes retries safe

DevFeed: [Idempotency keys: the API contract that makes retries safe](<https://devfeed.tech/articles/idempotency-keys-the-api-contract-that-makes-retries-safe-85160.md>)

Original publisher: [Read original article](<https://ankit-rana.com/logs/65-idempotency-keys-api-contract/>)

Author: hello@ankit-rana.com

Published: 2026-10-12T00:00:00Z

Content type: tutorial

Language: en

Sources: [Ankit Rana | Mechanical Sympathy](<https://devfeed.tech/sources/ankit-rana-mechanical-sympathy.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [database-consistency](<https://devfeed.tech/topics/database-consistency.md>), [retry](<https://devfeed.tech/topics/retry.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [event-sourcing](<https://devfeed.tech/topics/event-sourcing.md>), [CAP theorem](<https://devfeed.tech/topics/cap-theorem.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-design](<https://devfeed.tech/tags/api-design.md>), [application](<https://devfeed.tech/tags/application.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [database](<https://devfeed.tech/tags/database.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [exactly-once](<https://devfeed.tech/tags/exactly-once.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [keys](<https://devfeed.tech/tags/keys.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [retries](<https://devfeed.tech/tags/retries.md>), [transaction](<https://devfeed.tech/tags/transaction.md>)

### AI overview

The article explains how API idempotency keys make retries safe when a client cannot tell whether a timed-out request succeeded. It covers reserving keys atomically, validating repeated requests, replaying stored responses, coordinating external side effects with providers, and the limits imposed by key expiry.

### Source excerpt

A client that times out cannot distinguish a request that failed from one that succeeded with a lost response, so it must retry, and without an idempotency key that retry duplicates the write. The key has to be reserved before the work begins, in the same transaction, so two concurrent copies of the same request cannot both pass the check. The stored response must then be replayed verbatim, because recomputing it can return a different answer than the one the first caller received.

## Every Retry You Added Made the Outage Worse

DevFeed: [Every Retry You Added Made the Outage Worse](<https://devfeed.tech/articles/every-retry-you-added-made-the-outage-worse-63836.md>)

Original publisher: [Read original article](<https://blog.devops.dev/every-retry-you-added-made-the-outage-worse-f49e6437a8e3?source=rss----33f8b2d9a328---4>)

Author: Daniel Valev

Published: 2026-10-02T08:04:42Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [retry](<https://devfeed.tech/topics/retry.md>), [site-reliability-engineering](<https://devfeed.tech/topics/site-reliability-engineering.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [database](<https://devfeed.tech/tags/database.md>), [devops](<https://devfeed.tech/tags/devops.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [http](<https://devfeed.tech/tags/http.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [microservice-architecture](<https://devfeed.tech/tags/microservice-architecture.md>), [programming](<https://devfeed.tech/tags/programming.md>), [python](<https://devfeed.tech/tags/python.md>), [retry](<https://devfeed.tech/tags/retry.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [storm](<https://devfeed.tech/tags/storm.md>)

### AI overview

The excerpt says retries can amplify an outage: in a three-hop service chain where each layer retries a failed request three times, a healthy database receives one call, but a database outage can trigger 27 calls. Retries help with brief, independent failures such as dropped packets or rescheduled pods. When multiple layers--such as an HTTP client, service mesh, and cloud SDK--each retry, their locally reasonable policies combine without anyone owning the total; if the backend is failing from overload, added calls can worsen the failure. The excerpt ends before describing the discipline or steps proposed to prevent this.

### Source excerpt

Three layers that each try three times turn one failed query into 27 database calls. Here's the math, and the discipline that stops it Continue reading on DevOps.dev "

## Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments

DevFeed: [Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments](<https://devfeed.tech/articles/stateless-mcp-removes-session-affinity-requirements-for-aws-server-deployments-59805.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/09/aws-stateless-mcp/>)

Author: Leela Kumili

Published: 2026-09-25T12:58:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [session affinity](<https://devfeed.tech/topics/session-affinity.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [Server](<https://devfeed.tech/topics/server.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [retry](<https://devfeed.tech/topics/retry.md>), [Security](<https://devfeed.tech/topics/security.md>), [context](<https://devfeed.tech/topics/context.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-architecture](<https://devfeed.tech/tags/ai-architecture.md>), [ai-ml-data-engineering](<https://devfeed.tech/tags/ai-ml-data-engineering.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-stateless-mcp](<https://devfeed.tech/tags/aws-stateless-mcp.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [development](<https://devfeed.tech/tags/development.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [distributed-tracing](<https://devfeed.tech/tags/distributed-tracing.md>), [frameworks](<https://devfeed.tech/tags/frameworks.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [load-balancing](<https://devfeed.tech/tags/load-balancing.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [ml-data-engineering](<https://devfeed.tech/tags/ml-data-engineering.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [model-context-protocol-mcp](<https://devfeed.tech/tags/model-context-protocol-mcp.md>), [news](<https://devfeed.tech/tags/news.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [retries](<https://devfeed.tech/tags/retries.md>), [routing](<https://devfeed.tech/tags/routing.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [servers](<https://devfeed.tech/tags/servers.md>), [session-affinity](<https://devfeed.tech/tags/session-affinity.md>), [w3c](<https://devfeed.tech/tags/w3c.md>)

### AI overview

AWS explains that the latest Model Context Protocol specification removes protocol-level sessions, sticky-session requirements, and session storage for remote MCP servers. This enables independent request routing and simpler horizontal scaling, while shifting application state, retries, observability, and idempotency responsibilities to other layers.

### Source excerpt

AWS details how the latest Model Context Protocol specification removes protocol-level sessions, sticky-session requirements, and session storage for remote MCP servers. The change enables independent request routing and simpler horizontal scaling while shifting application state, retries, observability, and idempotency concerns to other layers. By Leela Kumili

## Multi-Table Transactions with Iceberg REST Catalogs and Apache Polaris

DevFeed: [Multi-Table Transactions with Iceberg REST Catalogs and Apache Polaris](<https://devfeed.tech/articles/multi-table-transactions-with-iceberg-rest-catalogs-and-apache-polaris-59928.md>)

Original publisher: [Read original article](<https://www.dremio.com/blog/multi-table-transactions-with-iceberg-rest-catalogs-and-apache-polaris/>)

Author: Alex Merced

Published: 2026-09-25T12:43:08Z

Content type: tutorial

Language: en

Sources: [Dremio](<https://devfeed.tech/sources/dremio.md>)

Topics: [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [REST](<https://devfeed.tech/topics/rest.md>), [client](<https://devfeed.tech/topics/client.md>), [retry](<https://devfeed.tech/topics/retry.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [test](<https://devfeed.tech/topics/test.md>), [Server](<https://devfeed.tech/topics/server.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-polaris](<https://devfeed.tech/tags/apache-polaris.md>), [commit](<https://devfeed.tech/tags/commit.md>), [data-lakehouse](<https://devfeed.tech/tags/data-lakehouse.md>), [dremio-blog-open-data-insights](<https://devfeed.tech/tags/dremio-blog-open-data-insights.md>), [iceberg](<https://devfeed.tech/tags/iceberg.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [rest](<https://devfeed.tech/tags/rest.md>), [retries](<https://devfeed.tech/tags/retries.md>), [schema](<https://devfeed.tech/tags/schema.md>), [table](<https://devfeed.tech/tags/table.md>), [test](<https://devfeed.tech/tags/test.md>), [transactions](<https://devfeed.tech/tags/transactions.md>)

### AI overview

A practical guide to multi-table transaction commits in Iceberg REST catalogs and Apache Polaris. It explains the optional REST commit endpoint, catalog-level atomicity, client support, conflict detection, retries, failure semantics, request and response structures, and validation steps.

### Source excerpt

Explore Iceberg REST multi-table commit semantics, atomicity, conflict handling, client support, and the role of Apache Polaris in coordinated commits. The post Multi-Table Transactions with Iceberg REST Catalogs and Apache Polaris appeared first on Dremio.

## Why AI Agent Actions Need Explicit Unknown States, Idempotency, and Reconciliation

DevFeed: [Why AI Agent Actions Need Explicit Unknown States, Idempotency, and Reconciliation](<https://devfeed.tech/articles/your-ai-agent-needs-an-unknown-state-59973.md>)

Original publisher: [Read original article](<https://hackernoon.com/your-ai-agent-needs-an-unknown-state?source=rss>)

Author: Dmytro Nasyrov

Published: 2026-09-25T11:25:54Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [execution](<https://devfeed.tech/topics/execution.md>), [retry](<https://devfeed.tech/topics/retry.md>), [permission](<https://devfeed.tech/topics/permission.md>), [service](<https://devfeed.tech/topics/service.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-reliability](<https://devfeed.tech/tags/ai-agent-reliability.md>), [ai-agent-security](<https://devfeed.tech/tags/ai-agent-security.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [human-in-the-loop](<https://devfeed.tech/tags/human-in-the-loop.md>), [human-in-the-loop-ai](<https://devfeed.tech/tags/human-in-the-loop-ai.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [permission](<https://devfeed.tech/tags/permission.md>), [reconciliation](<https://devfeed.tech/tags/reconciliation.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [service](<https://devfeed.tech/tags/service.md>), [timeout](<https://devfeed.tech/tags/timeout.md>), [tool-execution](<https://devfeed.tech/tags/tool-execution.md>)

### AI overview

The article explains that a timeout or lost response does not prove an AI agent action failed. It argues for explicit unknown outcomes, investigation and reconciliation before retrying consequential operations, along with idempotency or provider guarantees that make repetition safe.

### Source excerpt

A timeout does not prove an AI agent's action failed. Here's how explicit unknown states, idempotency, and reconciliation can prevent duplicate effects.

## Durable Execution for AI Agents: LangGraph, DBOS, Inngest and Temporal Compared

DevFeed: [Durable Execution for AI Agents: LangGraph, DBOS, Inngest and Temporal Compared](<https://devfeed.tech/articles/durable-execution-for-ai-agents-langgraph-dbos-inngest-and-temporal-compared-59665.md>)

Original publisher: [Read original article](<https://hackernoon.com/durable-execution-for-ai-agents-langgraph-dbos-inngest-and-temporal-compared?source=rss>)

Author: Paolo Perrone

Published: 2026-09-24T19:00:31Z

Content type: comparison

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Langgraph](<https://devfeed.tech/topics/langgraph.md>), [execution](<https://devfeed.tech/topics/execution.md>), [Database](<https://devfeed.tech/topics/database.md>), [retry](<https://devfeed.tech/topics/retry.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [backend](<https://devfeed.tech/tags/backend.md>), [database](<https://devfeed.tech/tags/database.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [langgraph](<https://devfeed.tech/tags/langgraph.md>), [llms](<https://devfeed.tech/tags/llms.md>), [pythjon](<https://devfeed.tech/tags/pythjon.md>), [retry](<https://devfeed.tech/tags/retry.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [workflow-automation](<https://devfeed.tech/tags/workflow-automation.md>)

### AI overview

A comparison of durable-execution approaches for AI agents, covering how LangGraph, DBOS, Inngest, and Temporal save workflow state and recover after crashes. It explains checkpointing, replay, database-backed logs, retries, and the risk of losing model calls outside step boundaries.

### Source excerpt

Four ways to make an agent survive a crash. Where each one keeps its state, what it forces on your code, and which one you already have installed.

## How Intelligent Load Shedding Prevents Cascading Failures in Tier-0 Systems

DevFeed: [How Intelligent Load Shedding Prevents Cascading Failures in Tier-0 Systems](<https://devfeed.tech/articles/how-intelligent-load-shedding-prevents-cascading-failures-in-tier-0-systems-59460.md>)

Original publisher: [Read original article](<https://engineering.salesforce.com/how-intelligent-load-shedding-prevents-cascading-failures-in-tier-0-systems/>)

Author: Scott Nyberg

Published: 2026-09-24T16:56:36Z

Content type: article

Language: en

Sources: [Salesforce](<https://devfeed.tech/sources/salesforce-engineering-blog.md>)

Topics: [systems](<https://devfeed.tech/topics/systems.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [retry](<https://devfeed.tech/topics/retry.md>), [Automation](<https://devfeed.tech/topics/automation.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automation](<https://devfeed.tech/tags/automation.md>), [availability](<https://devfeed.tech/tags/availability.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [identity](<https://devfeed.tech/tags/identity.md>), [outage](<https://devfeed.tech/tags/outage.md>), [platform](<https://devfeed.tech/tags/platform.md>), [protection](<https://devfeed.tech/tags/protection.md>), [queuing](<https://devfeed.tech/tags/queuing.md>), [rate-limiting](<https://devfeed.tech/tags/rate-limiting.md>), [regions](<https://devfeed.tech/tags/regions.md>), [retries](<https://devfeed.tech/tags/retries.md>), [service](<https://devfeed.tech/tags/service.md>), [services](<https://devfeed.tech/tags/services.md>), [systems](<https://devfeed.tech/tags/systems.md>), [traffic](<https://devfeed.tech/tags/traffic.md>), [upstream](<https://devfeed.tech/tags/upstream.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

A Salesforce Engineering Q&A explains how the Cloud Atlas team protects a globally distributed identity data store from cascading failures. It describes intelligent load shedding, distributed rate limiting, and coordinator-free quota management used to isolate traffic spikes, protect tenants, and maintain high availability for authentication.

### Source excerpt

By Ramya Subramani and Prateek Vats In our Engineering Energizers Q&A series, we highlight the engineering minds driving innovation across Salesforce. Today, we spotlight Ramya Subramani, Vice President of Engineering. Ramya leads the Cloud Atlas team, which operates the globally distributed identity data store behind a large portion of Salesforce authentication. Every login and token [...] The post How Intelligent Load Shedding Prevents Cascading Failures in Tier-0 Systems appeared first on Salesforce Engineering Blog.

## 5 Resilience Patterns for AI Agents

DevFeed: [5 Resilience Patterns for AI Agents](<https://devfeed.tech/articles/5-resilience-patterns-for-ai-agents-59173.md>)

Original publisher: [Read original article](<https://thetshaped.dev/p/5-resilience-patterns-for-ai-agents-retries-checkpoints-idempotency>)

Author: The T-Shaped Dev

Published: 2026-09-24T10:19:30Z

Content type: tutorial

Language: en

Sources: [The T-Shaped Dev](<https://devfeed.tech/sources/the-t-shaped-dev.md>)

Topics: [Resilience](<https://devfeed.tech/topics/resilience.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [retry](<https://devfeed.tech/topics/retry.md>), [Stateful](<https://devfeed.tech/topics/stateful.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [anthropic](<https://devfeed.tech/topics/anthropic.md>)

Tags: [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [error](<https://devfeed.tech/tags/error.md>), [errors](<https://devfeed.tech/tags/errors.md>), [openai](<https://devfeed.tech/tags/openai.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [retries](<https://devfeed.tech/tags/retries.md>), [stateful](<https://devfeed.tech/tags/stateful.md>)

### AI overview

This practical article presents five resilience adjustments for production AI agents, including scoped step retries, idempotent tools, checkpoints, and run budgets. It explains why long, stateful, side-effecting agent runs require different failure-handling strategies than ordinary requests.

### Source excerpt

Checkpoints, scoped retries, idempotent tools, and run budgets: how production agents survive the failure math of 20-step loops.

## In Search of a Compositional Theory of Self-Stabilization

DevFeed: [In Search of a Compositional Theory of Self-Stabilization](<https://devfeed.tech/articles/in-search-of-a-compositional-theory-of-self-stabilization-57579.md>)

Original publisher: [Read original article](<https://muratbuffalo.blogspot.com/2026/09/in-search-of-compositional-theory-of.html>)

Author: Murat (noreply@blogger.com)

Published: 2026-09-21T16:55:13Z

Content type: article

Language: en

Sources: [Metadata](<https://devfeed.tech/sources/metadata.md>)

Topics: [distributed-systems](<https://devfeed.tech/topics/distributed-systems.md>), [retry](<https://devfeed.tech/topics/retry.md>), [systems](<https://devfeed.tech/topics/systems.md>)

Tags: [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [fault-tolerance](<https://devfeed.tech/tags/fault-tolerance.md>), [metastability](<https://devfeed.tech/tags/metastability.md>), [retries](<https://devfeed.tech/tags/retries.md>), [stabilization](<https://devfeed.tech/tags/stabilization.md>), [tla-plus](<https://devfeed.tech/tags/tla-plus.md>)

### AI overview

The author examines compositional reasoning for self-stabilization and metastable failures. Using a TLA+ model of a retry storm, the article discusses rely-guarantee contracts, their limitations for modeling accumulating queues, and possible directions for a compositional theory.

### Source excerpt

My quest for a principled solution for metastable failures has taken me back to my roots on self-stabilization, as this recent paper related the problem to composition of self-stabilizing systems. But, my literature search for recent work on composing self-stabilizing systems didn't yield anything useful. The layered stabilization idea was already in place by the early 2000s, and nothing fundamental seems to have been added since. Frustrating. So I decided to attack the problem using the concrete example I have. I had composed a rely-guarantee TLA+ model of a retry storm as two components with contracts. That model reproduces metastable failure because the composition that worked from good states failed to work when a large shock removes the base case that let the two conditions hold each other up. Searching for rely-guarantee based composition from every state, turned up a 2017 control theory paper by Kim, Arcak and Seshia, "A Small Gain Theorem for Parametric Assume-Guarantee Contracts". This paper does roughly what I want: discharging circular reasoning between two components without layering or blocking. But it comes with some serious limitations. In their formalism, a component is an input-output relation on signals, and contracts relate an input bound to an output bound. This is a memoryless view of a component, so it is not possible to express backlog accumulating from previous rounds. That rules out queues, among other useful distributed systems concepts. It also has no connection to stabilization. The paper does not talk about a variant/potential function and convergence reasoning. But there are still pieces there worth stealing toward a compositional theory of self-stabilization and metastability. Below I try to work this out... somewhat unsuccessfully. Understanding Parametric Assume-Guarantee Contracts In our original model, the retrier's guarantee was conditional and partial: "if the queue is under 6, I send no retries". This contract does not say anyth

[Next page](<https://devfeed.tech/topics/retry.md?cursor=WyIyMDI2LTA5LTIxVDE2OjU1OjEzKzAwOjAwIiwgIjgwYWM3M2E2LTg1OTktNDRhNi04YTFkLWU4OGRiZjZhNmI2NSJd>)