Skip to content
Tagged articles

Retry Logic

16 articles · Page 1 of 1
Data Bricklaying Diary
Data Bricklaying Diary
Nov 10, 2026 · Backend Development

Why 'Completed' Doesn't Mean Done: Verifying Order Creation After Timeouts & Retries

This article explains why an AI agent's 'completed' message can hide duplicate purchase orders after API timeouts, detailing how to verify actual creation status, implement idempotent retries with stable request IDs, distinguish cancellation from revocation, and test failure scenarios using concrete examples like REQ01 and PO8601.

API DesignIdempotencyRetry Logic
0 likes · 19 min read
Why 'Completed' Doesn't Mean Done: Verifying Order Creation After Timeouts & Retries
Java Architect Essentials
Java Architect Essentials
Nov 4, 2026 · Artificial Intelligence

GPT Pro for Complex Systems: Structured Workflow Beats Raw Speed Claims

The article warns that GPT Pro's speed on complex system code isn't universally guaranteed and recommends a structured workflow: provide service boundaries, call chains, and reproduction steps; analyze one risk point at a time (e.g., idempotency key failure in retries); review diffs in isolated branches; run integration, stress, and regression tests before deployment.

AI-assisted developmentGPT ProIdempotency
0 likes · 3 min read
GPT Pro for Complex Systems: Structured Workflow Beats Raw Speed Claims
Architecture Development Notes
Architecture Development Notes
Oct 30, 2026 · Artificial Intelligence

MCP Tool Errors ≠ JSON-RPC Failures: Two Recovery Paths Clients Must Keep

This article explains why MCP clients must distinguish between JSON-RPC protocol errors and tool business failures (isError: true), outlining three error categories—request unintelligible, tool execution failure, and result validation failure—and showing how proper separation enables correct retry logic, user feedback, and audit logging.

JSON-RPCMCPProtocol Design
0 likes · 8 min read
MCP Tool Errors ≠ JSON-RPC Failures: Two Recovery Paths Clients Must Keep
Data Bricklaying Diary
Data Bricklaying Diary
Oct 29, 2026 · Artificial Intelligence

Why Agent Bills Spiral Out of Control: Total Task Accounting, Retry Amplification, and Budget Guardrails

The article explains how AI Agent costs escalate through untracked token usage, tool calls, resource occupancy, and layered retries, and proposes a budget framework that reserves funds atomically at the execution layer, caps retries with safety checks, preserves progress on exhaustion, and evaluates cost against acceptance rates and human rework.

AI AgentAWS retry guidanceRetry Logic
0 likes · 9 min read
Why Agent Bills Spiral Out of Control: Total Task Accounting, Retry Amplification, and Budget Guardrails
IT Architects Alliance
IT Architects Alliance
Oct 21, 2026 · Artificial Intelligence

AI Agent Harness Value: Correction Gains vs. Fixed Costs

This article analyzes the ROI of behavior harnesses for AI agents using a BFF timeout-retry case study, showing how harnesses turn omissions into fixable signals, distinguishing runtime recovery from development-time correction, and calculating break-even points where per-run savings offset fixed harness investment.

AI AgentBFFBehavior Harness
0 likes · 15 min read
AI Agent Harness Value: Correction Gains vs. Fixed Costs
Architecture Development Notes
Architecture Development Notes
Oct 18, 2026 · Artificial Intelligence

Claude Code Bug: Message Interruption Misreported as User Refusal

Claude Code 2.1.301 fixed a bug where tool calls interrupted by user messages during permission checks were incorrectly logged as user refusals, conflating explicit decisions with scheduling cancellations; the article argues for a distinct 'not_executed' status with cause and retryable fields to preserve accurate model behavior and audit metrics.

AI AgentClaude CodeRetry Logic
0 likes · 9 min read
Claude Code Bug: Message Interruption Misreported as User Refusal
IT Architects Alliance
IT Architects Alliance
Oct 9, 2026 · Backend Development

API Timeout After Ticket Creation: Why Query-First Recovery Beats Blind Retries

When an API times out after creating a ticket, the system must treat the result as unknown rather than failed, using persistent operation IDs to query the business service, relying on idempotency contracts for safe retries, and escalating to manual review only after exhausting a time-bounded recovery budget.

API timeoutAgent RuntimeIdempotency
0 likes · 28 min read
API Timeout After Ticket Creation: Why Query-First Recovery Beats Blind Retries
Data Bricklaying Diary
Data Bricklaying Diary
Oct 7, 2026 · Backend Development

Agent Error Recovery: Why Retries Alone Fail — Idempotency & Reconciliation

This article explains why automatic retries after agent timeouts can duplicate business actions, and details how to distinguish call failures from executed side effects, implement execution-side idempotency guarantees, reconcile using original action identifiers, and define safe recovery rules with human escalation when outcomes remain unknown.

IdempotencyRetry Logicagent systems
0 likes · 17 min read
Agent Error Recovery: Why Retries Alone Fail — Idempotency & Reconciliation
Open Source Tech Hub
Open Source Tech Hub
Sep 6, 2026 · Backend Development

Designing Reliable Failure Boundaries in PHP: Errors, Exceptions & Result Types

This article explores how to design robust failure boundaries in PHP payment systems by distinguishing validation errors, expected business declines, transient provider failures, and programming defects, using result types for normal outcomes, translated exceptions for integration failures, idempotent retries, and observability without sensitive data.

IdempotencyObservabilityPHP
0 likes · 38 min read
Designing Reliable Failure Boundaries in PHP: Errors, Exceptions & Result Types
Coder Trainee
Coder Trainee
Aug 27, 2026 · Operations

How a DNS Resolution Failure Prompted a Full Network Layer Investigation

An intermittent DNS resolution failure caused third‑party API timeouts, leading to a step‑by‑step investigation that revealed an unstable public DNS server, and resulted in four practical solutions including switching DNS servers, adjusting JVM cache settings, adding hosts entries, and implementing retry logic.

DNSJVM cacheRetry Logic
0 likes · 6 min read
How a DNS Resolution Failure Prompted a Full Network Layer Investigation
samdeepthink
samdeepthink
Aug 13, 2026 · Backend Development

How to Write Robust Code When Integrating Third‑Party APIs: A Real‑World Example

The article walks through a production scenario where business documents must be synchronized to a low‑code platform via its OpenAPI, explaining how to build a unified client, verify apparent failures, apply a single retry, and fall back to a task table for asynchronous recovery, all illustrated with concrete code.

API integrationRetry Logicbackend development
0 likes · 11 min read
How to Write Robust Code When Integrating Third‑Party APIs: A Real‑World Example
macrozheng
macrozheng
Apr 23, 2023 · Backend Development

Master Spring Retry: Using @Retryable and @Recover for Robust Backend Retries

This guide explains how to use Spring Retry’s @Retryable and @Recover annotations in Spring Boot, covering dependency setup, enabling retries, annotating methods, configuring backoff policies, handling exhausted retries, and important precautions for reliable backend retry mechanisms.

@RetryableJavaRetry Logic
0 likes · 7 min read
Master Spring Retry: Using @Retryable and @Recover for Robust Backend Retries
Java Backend Technology
Java Backend Technology
Apr 17, 2023 · Backend Development

12 Common Pitfalls When Integrating Third‑Party APIs and How to Fix Them

This article outlines the most frequent problems encountered when calling third‑party APIs—such as domain inaccessibility, signature errors, token expiration, missing data, timeouts, and undocumented changes—and provides practical solutions and best‑practice recommendations for backend developers.

API integrationRetry Logicerror handling
0 likes · 15 min read
12 Common Pitfalls When Integrating Third‑Party APIs and How to Fix Them
Su San Talks Tech
Su San Talks Tech
Apr 16, 2023 · Backend Development

13 Common Pitfalls When Integrating Third‑Party APIs and How to Fix Them

This article outlines the most frequent problems developers encounter when calling third‑party APIs—such as unreachable domains, signature errors, token expiration, timeouts, and inconsistent documentation—and provides practical solutions and best‑practice recommendations to keep integrations reliable.

API integrationRetry Logicerror handling
0 likes · 15 min read
13 Common Pitfalls When Integrating Third‑Party APIs and How to Fix Them
Architecture Digest
Architecture Digest
Oct 10, 2022 · Operations

Designing Fault‑Tolerant Microservices: Patterns and Practices

This article explains how to build highly available microservice systems by applying fault‑tolerance patterns such as graceful degradation, health checks, self‑healing, failover caches, retries, rate limiting, bulkhead isolation, circuit breakers, and systematic failure testing, while also covering change‑management and deployment strategies.

Circuit BreakerRetry Logicfault tolerance
0 likes · 14 min read
Designing Fault‑Tolerant Microservices: Patterns and Practices