Healthcare · claims

How a claims-intake team replaced a home-grown queue and retry layer with durable workflows in two sprints.

2,318 lines of queue code deleted

0 claims lost to crashes

2 sprints to migrate

The pager for stuck jobs used to go off weekly. It hasn’t gone off since March.

Maya Okafor

Staff engineer

Halvard Health

Halvard Health case study cover

Where they started

Halvard processes around 60,000 insurance claims a week. Intake ran on a queue, three worker services and a retry table that nobody fully trusted. When a worker died mid-claim, an engineer would find the half-finished record the next morning.

What they built

Each claim became one workflow run: extract, validate, check eligibility, price and file. Every call to a payer system is a step with retries and an idempotency key, so a timeout never files a claim twice.

Claims that fail validation now pause for a reviewer instead of landing in a dead-letter queue. The reviewer fixes the field in the dashboard and the run resumes at the next step.

What changed

The retry table and the queue are gone. On-call went from a weekly stuck-job page to none since March, and the team ships intake changes on Tuesdays instead of waiting for quiet weeks.

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.