September 2026 Summaries

Inngest’s multi-tenant durable execution queue schedules hundreds of millions of jobs while ensuring that high-volume customers cannot starve others and that queued work survives failures. Inspired by Apple’s QuiCK system, it uses a red-black tree ordered by job due time, with a sliding time window that selects ready work and reschedules jobs blocked by concurrency or throttle limits. The platform separates scheduling data in the queue from execution state in a state store, allowing retries to resume without repeating completed steps. Although Valkey has supported the queue, its memory limits, recovery risks, and single-threaded operation make true per-tenant fairness difficult at scale, particularly when many jobs are blocked or tenants have many distinct keys. Inngest is therefore migrating toward FoundationDB, whose disk-based, replicated, multi-threaded architecture can process due work across tenant lanes in parallel. The article argues that simple queues may suit lower-volume or non-fairness-sensitive workloads, but durable multi-tenant workflow scheduling requires careful data-layout, storage, fairness, retry, and flow-control design.

Inngest describes its staged approach to deploying major infrastructure changes, which is intended to improve reliability, performance, and scalability while limiting risks to customer workloads. Changes undergo internal testing, load benchmarking, and trials on the company’s own accounts before being released to small groups of Hobby users, whose non-business-critical environments provide an opportunity to observe varied real-world production behavior with a limited blast radius. Although Hobby users may occasionally encounter temporary performance degradation during these releases, Inngest says it monitors results closely and resolves issues before expanding changes to additional users. Pro and Enterprise accounts are initially excluded and receive stronger infrastructure isolation, with paid upgrades automatically moving accounts out of the Hobby rollout pool. Users experiencing latency or other issues can seek help through support requests, Discord, the status page, or dedicated Enterprise Slack channels, while the company states it will continue investing in safeguards, monitoring, and isolation to support dependable platform operations.

On September 4, 2026, Inngest experienced a platform-wide function execution outage from 18:13 to 18:48 UTC after a network change intended to connect a new data center removed a Virtual Private Gateway that also supported the active AWS Direct Connect path for the existing data center. The loss of this private connection prevented critical execution services from reaching AWS-hosted state services, disrupting scheduling and function processing, although events continued to be accepted. Restoring the VPC attachment did not immediately resolve the issue because the Direct Connect association also had to be restored separately, and service recovery began once connectivity returned. Inngest identified insufficient network redundancy as a contributing design weakness and plans to strengthen change controls, complete new data center connectivity, and build redundant paths and failover capabilities. Queued work resumed processing after recovery, but some affected runs may require replay.