Engineering

Retries are not durability

A retry repeats a call. Durability remembers what already happened. Why the difference decides whether your agent refunds a customer once or twice.

Lena Ferris

Founding engineer

7 min read

Retries are not durability cover

Every team that puts an LLM agent into production writes a retry loop in the first week. It feels like reliability. It isn’t, quite.

A retry doesn’t know what finished

When a function with five external calls fails on the fifth, a retry starts again at the first. The four calls that already succeeded run again: another charge lookup, another refund, another email.

Durability records each step

A durable workflow saves the result of each step as it finishes. On a retry or a replay, finished steps return their saved results instead of running again. Only the step that failed runs again.

What it costs you

You wrap each external call in a named step. That’s the entire change, and it’s the difference between an incident and a log line.

Get started

Ship the agent. Keep the receipts.

Free for 50,000 steps a month. No credit card, no separate workers, and your first durable workflow deployed before lunch.

orrindel

Durable runtime for AI agents and automations. Every run, in plain text.

Book a 20-minute demo →
All systems normal
99.99% uptime · last 90 days
90 days agotoday
regions us-east · eu-west · ap-south
soc 2 type ii · gdpr · hipaa (baa)
sdk v4.2.1 · node · python · go
© 2026 Orrindel Labs, Inc.PrivacyTermsSecurityMade in plain text.

Create a free website with Framer, the website builder loved by startups, designers and agencies.