What problem does it solve? Managing external API rate limits, preventing duplicate work from event bursts, and ensuring fair resource distribution across tenants are common challenges in event-driven systems. This Skill provides prescriptive guidance for applying Inngest's flow control primitives to keep background functions reliable and within quota. ## Core Features & Use Cases - Concurrency & Throttling: Limit simultaneous step execution or function starts per key, protecting databases and third-party APIs like OpenAI or Stripe from overload. - Debounce, Singleton & Rate Limiting: Collapse rapid event bursts into a single run, skip or cancel duplicate runs, and discard excessive events within a time window. - Priority & Batching: Give important runs queue priority based on event data, and process grouped events together for efficient bulk operations. - Use Case: When OpenAI returns 429 errors under load, apply account-scoped concurrency of 60 calls plus per-user keyed concurrency so all functions share the quota fairly while individual users stay isolated. ## Quick Start Ask the AI to add per-user concurrency limits and throttling to your Inngest function so it respects a third-party API rate limit.