inngest-flow-control

Use throttling to limit function starts per period, or account-level concurrency with a shared key like "openai" to cap simultaneous API calls across all functions. Throttling delays excess runs while rate limiting discards them.

Throttling delays function runs to spread them over a time period, while rate limiting discards events that exceed the limit. Use throttling to respect API quotas and rate limiting to skip duplicate or abusive events.

Add a debounce configuration with a period and key, such as waiting 5 minutes after the last document edit before saving. Inngest processes only the latest event once activity stops, with an optional timeout to force execution.

Concurrency limits executing steps, not function runs. A function waiting on step.sleep() or step.waitForEvent() does not count against the concurrency limit, so limits reflect actual code execution.

Yes, you can combine throttling, concurrency, priority, and other options in one function definition. A common pattern pairs global throttling for API limits with per-user concurrency keys for tenant fairness and priority for paid plans.

The examples are TypeScript-focused, but the core concepts apply across languages. For Python or Go syntax, refer to the official Inngest documentation for language-specific configuration details.