NEW: Bursty Concurrency—Coverage for Spikes

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.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.