--- title: NEW: Bursty Concurrency—Coverage for Spikes | daily.dev description: Inngest launched a new feature called bursty concurrency, which temporarily raises an account's concurrency ceiling to 3x its plan limit for up to one hour per... canonical: https://daily.dev/posts/new-bursty-concurrency-coverage-for-spikes-oywvtwix8 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: NEW: Bursty Concurrency—Coverage for Spikes | daily.dev og:description: Inngest launched a new feature called bursty concurrency, which temporarily raises an account's concurrency ceiling to 3x its plan limit for up to one hour per... og:url: https://daily.dev/posts/new-bursty-concurrency-coverage-for-spikes-oywvtwix8 og:image: https://api.daily.dev/og/posts/OYwvtwix8.png og:image:alt: NEW: Bursty Concurrency—Coverage for Spikes og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # NEW: Bursty Concurrency—Coverage for Spikes **[Inngest Blog](https://daily.dev/sources/inngest)** · 5 min read · 0 upvotes · 0 comments ## Summary Inngest launched a new feature called bursty concurrency, which temporarily raises an account's concurrency ceiling to 3x its plan limit for up to one hour per month, letting unexpected spikes in workload run immediately instead of queuing into a backlog. The feature is free for Pro and above accounts, counted in minutes of burst usage, resets monthly, and triggers admin notifications at 25%, 50%, 75%, and 100% of the budget so teams can decide whether to permanently raise their concurrency limit. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is Inngest's bursty concurrency feature and how much extra capacity does it provide? Bursty concurrency lets an Inngest account run up to 3x its plan's concurrency ceiling for a total of one hour per month, so a sudden spike in work runs immediately instead of queuing into a backlog. It applies automatically at the start of a burst, is measured in minutes (each minute any burst capacity is used counts against the monthly 60), resets monthly, and is free on Pro and above plans. Admins get notifications at 25%, 50%, 75%, and 100% of the budget. _Teams sizing concurrency limits for spiky workloads can track platform changes like this via daily.dev._ ### Does a run waiting on a human approval or external event count against Inngest's concurrency limit? No, runs with wait-for steps hold no concurrency slot. A run that is sleeping, waiting for an event, or paused between steps does not count, so an agent waiting days for human approval uses zero concurrency until it actually has work to execute. This differs from traditional job queues, where a paused job usually still holds its worker the entire time unless manually split into separate jobs. _Developers comparing queue-based systems to durable execution platforms can follow these distinctions on daily.dev._ ## Similar posts on daily.dev - [No more QPS limits on Developer Plans](https://daily.dev/posts/no-more-qps-limits-on-developer-plans-genb9im5w) · Tinybird · 5 upvotes · 0 comments - [Introducing Firebase spend caps](https://daily.dev/posts/introducing-firebase-spend-caps-iygfnrfcv) · Firebase · 0 upvotes · 0 comments - [Spend Management expands to Enterprise Flexible Commitment plans](https://daily.dev/posts/spend-management-expands-to-enterprise-flexible-commitment-plans-gsqearxhz) · Vercel · 3 upvotes · 0 comments - [Scaling responsibly: evolving our API rate limits to power the next generation of Atlassian Cloud](https://daily.dev/posts/scaling-responsibly-evolving-our-api-rate-limits-to-power-the-next-generation-of-atlassian-cloud-5kwexxc0w) · Atlassian · 0 upvotes · 0 comments - [Introducing Organization Spending Limits](https://daily.dev/posts/introducing-organization-spending-limits-rykzhewgx) · Neon · 39 upvotes · 2 comments --- Tags: [#workflow-orchestration](https://daily.dev/tags/workflow-orchestration), [#inngest](https://daily.dev/tags/inngest) [View this post on daily.dev](https://daily.dev/posts/new-bursty-concurrency-coverage-for-spikes-oywvtwix8) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"NEW: Bursty Concurrency—Coverage for Spikes","url":"https://daily.dev/posts/new-bursty-concurrency-coverage-for-spikes-oywvtwix8","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/new-bursty-concurrency-coverage-for-spikes-oywvtwix8"},"datePublished":"2026-10-06T21:50:58.132Z","dateModified":"2026-10-06T22:09:25.004Z","description":"Inngest launched a new feature called bursty concurrency, which temporarily raises an account's concurrency ceiling to 3x its plan limit for up to one hour per...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8085ae2a1ceb2180c7456c29ddd4bbe8?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8085ae2a1ceb2180c7456c29ddd4bbe8?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Inngest Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Inngest Blog","logo":"https://media.daily.dev/image/upload/s--ieZKUa5y--/c_limit,w_256/f_auto,q_auto/v1789329423/logos/inngest?_a=BAMAMicg0","url":"https://daily.dev/sources/inngest"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/new-bursty-concurrency-coverage-for-spikes-oywvtwix8","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"workflow-orchestration,inngest","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Inngest Blog","item":"https://daily.dev/sources/inngest"},{"@type":"ListItem","position":3,"name":"NEW: Bursty Concurrency—Coverage for Spikes"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/new-bursty-concurrency-coverage-for-spikes-oywvtwix8#faq","mainEntity":[{"@type":"Question","name":"What is Inngest's bursty concurrency feature and how much extra capacity does it provide?","acceptedAnswer":{"@type":"Answer","text":"Bursty concurrency lets an Inngest account run up to 3x its plan's concurrency ceiling for a total of one hour per month, so a sudden spike in work runs immediately instead of queuing into a backlog. It applies automatically at the start of a burst, is measured in minutes (each minute any burst capacity is used counts against the monthly 60), resets monthly, and is free on Pro and above plans. Admins get notifications at 25%, 50%, 75%, and 100% of the budget. Teams sizing concurrency limits for spiky workloads can track platform changes like this via daily.dev."}},{"@type":"Question","name":"Does a run waiting on a human approval or external event count against Inngest's concurrency limit?","acceptedAnswer":{"@type":"Answer","text":"No, runs with wait-for steps hold no concurrency slot. A run that is sleeping, waiting for an event, or paused between steps does not count, so an agent waiting days for human approval uses zero concurrency until it actually has work to execute. This differs from traditional job queues, where a paused job usually still holds its worker the entire time unless manually split into separate jobs. Developers comparing queue-based systems to durable execution platforms can follow these distinctions on daily.dev."}}]} ```