October 2026 Summaries

No summary generated yet.

Inngest has introduced Bursty Concurrency for Pro and higher plans, allowing accounts to temporarily run up to three times their normal concurrency limit for one hour each month at no additional cost. The feature is intended to prevent backlogs during unexpected workload spikes caused by fan-outs, webhook replays, scheduled jobs, imports, branching agents, or slower external services. Concurrency measures actively executing steps, while runs waiting for events, approvals, or timers do not consume slots. Under the new system, an account with a limit of 100 can process up to 300 concurrent steps during a burst, with usage measured by the minutes in which burst capacity is used rather than by the number of steps. Administrators receive notifications as they consume 25%, 50%, 75%, and 100% of the monthly budget, and the feature can help customers determine whether occasional spikes are temporary or indicate a need for a permanent concurrency increase. Function-level concurrency settings override burst capacity, and workloads regularly exceeding the temporary ceiling or reaching peaks above 1,000 may require upgraded or Enterprise pricing.

Lauren Craigie uses finishing last in a 50-kilometer ultramarathon as a metaphor for Inngest’s new “people building for the long run” campaign, which focuses on making complex, lengthy workflows more resilient. The article argues that AI-driven, non-deterministic, and human-in-the-loop processes increasingly require systems that can handle delays, retries, memory constraints, fan-outs, and unexpected inputs over extended periods. Inngest is presented as a workflow infrastructure platform that lets developers wrap functions in durable steps, observe performance, and manage failures without operating separate workers or queues, using a single SDK. The campaign targets a broad range of production builders, from engineers to less technical creators, and includes community running events in San Francisco and New York City, including New York’s Founder's Run Club on October 17 and marathon weekend activities.

Long-running software work, including data pipelines, AI agents, approval processes, and webhook-driven tasks, is vulnerable to crashes, resource exhaustion, and external delays when it is designed like a short-lived request. Drawing on a healthtech pipeline that repeatedly failed overnight because its progress existed largely in memory, the article argues that reliable systems must be designed to recover from failures in the middle of execution rather than restart from the beginning. It recommends dividing work into short, durable steps that save results as they complete, using memoization and idempotency keys to safely resume work without repeating side effects, and storing orchestration state outside individual worker processes. It also advises releasing compute resources during waits, distributing large datasets across many isolated chunks instead of a single massive job, and applying flow control to protect dependent systems. The author presents Inngest as a platform that provides these durable-execution capabilities, allowing runs to span long periods while individual steps remain short, retryable, and resilient to deployments or worker failures.