Blog Article

What dead f*cking last taught me about durable execution

Lauren CraigieOct 2, 20263 min read

I DFL'ed my first 50k. If you have even one hometown turkey trot under your belt you know what a DNF is—Did Not Finish. If you went out the night before, it's a DNS—Did Not Start. But a DFL? A DFL means I finished Dead F*cking Last.

Which is actually a flex for two reasons:

  1. There's a course limit—runners get pulled off if they won't finish in time.
  2. The course limit is 12 hours.

12 hours! I ran (loosely defined) for 12 hours up and down a mountain. Way longer than the winner who finished in half the time.

This week Inngest kicked off a new campaign inspired by my heroic feat people building for the long run.

Because like the angelic aid station volunteers, Inngest keeps what you build running with pauses, retries, fan-outs… it's the gummy bears and pickle juice of workflow infrastructure.

This campaign is for things that run long—people, apps, and agents alike.

No surprises on the long run

While Inngest also makes fast, single-step functions durable, data from billions of runs over the last year tell us where things are moving: Long running, non-deterministic, human-in-the-loop workflows. Mostly driven by AI. And that's where things get weird.

Much like an ultra marathon, the longer the run, the more likely things are to happen:

Delayed start times | delayed API calls.

Running out of memory | running out of Oreos.

Unexpected user inputs | unexpected user outputs (💩).

Builders and runners alike don't want to think about any of this. They just want to go. They want all their weird workflows to keep running, no matter what.

Inngest makes that easy. Wrap existing functions in steps that tell your code exactly what to do during any event, at any scale. And like the coach that told you that Chipotle is not an appropriate pre-race meal, Inngest lets you score every part of the run so you know what worked, and what didn't.

One SDK, zero extra infrastructure.

Long running workflows for every long running human

On our recent CodeTv episode, Scott Moss from Netflix said it best, "Inngest was the most important thing in my stack, and the thing I thought about the least."

Inngest makes long running things boring. No workers, no queues, and no hunting for clues when things fail.

It used to just be technical founders and full-stack engineers that cared about this DX. Now it's anyone building in production—product engineers, platform engineers, GTM engineers… even vibe-coders who don't have time to parse through lots of excess code and logic.

Inngest is for all of them. And so is this campaign. It's for anyone up late, up early, addicted to caffeine, and running on pizza. For anyone building for their own long run.

Meet us out there

The Lonng Run campaign mug on a red background, with a cartoon mouth, a green wave, and a running can

We're starting in San Francisco and New York City, and you know I'll be there, Hokas and all.

San Francisco: Catch us at Corgi Cafe, and local runs in the city.

New York City: Join us at Founder's Run Club on Oct 17, and all marathon weekend.

Related content

Build better
agents today

Add Inngest to your project in minutes. Free to start, no credit card required.