inngest-flow-control — Claude Code skill: Inngest flow control
A skill covering Inngest flow control: concurrency, throttling, rate limiting, debounce, priority, singleton and event batching. Useful when external APIs return 429s.
npx skills add inngest/inngest-skills --skill inngest-flow-control -a claude-codeWhat inngest-flow-control does
The skill walks through every flow control option in Inngest and pairs each one with TypeScript examples. It opens with a decision guide: cap how many runs execute at once, spread starts over time, drop excess events, wait for activity to settle, or group events into batches. Each section then shows an inngest.createFunction config with the relevant parameters.
Concurrency limits executing steps rather than function runs, so a function parked on step.sleep() or step.waitForEvent() does not count against the limit. A key applies the limit per unique value, and scope: "account" shares one quota across functions — that matters when several of them call the same external API. Throttling controls function starts per period with a burst allowance. Rate limiting discards events instead of delaying them, which makes it a duplicate guard for webhooks rather than a traffic smoother.
Debounce waits for events to stop arriving and processes the last one; timeout forces the work through if edits never stop. Priority pushes a run ahead in the queue based on an expression over event data, and singleton keeps one instance per key. The skills target TypeScript — for Python and Go the authors point to the Inngest docs, so expect to translate the examples yourself.
What it helps with
- stay under an external API limit when several functions hit the same service
- stop duplicate work from a burst of webhooks
- save a document once, after the user stops editing
- give each tenant its own share of runs without noisy neighbours
- let a VIP order jump ahead of the queue
Example prompts for the agent
- Set up concurrency keyed on user_id so only one step runs per user
- Add throttling at 10 starts per minute keyed on customer_id for the CRM sync
- Debounce document saves for 5 minutes on document_id so it runs after the last edit
How to install inngest-flow-control
1Skills CLI (Vercel)
npx skills add inngest/inngest-skills --skill inngest-flow-control -a claude-code2Manually: put the files in place
~/.claude/skills/inngest-flow-control/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/inngest-flow-control/
1Skills CLI (Vercel)
npx skills add inngest/inngest-skills --skill inngest-flow-control -a codex2Manually: put the files in place
.agents/skills/inngest-flow-control/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add inngest/inngest-skills --skill inngest-flow-control -a cursor2Manually: put the files in place
.cursor/skills/inngest-flow-control/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install inngest/inngest-skills inngest-flow-control2Manually: put the files in place
.github/skills/inngest-flow-control/SKILL.md1Skills CLI (Vercel)
npx skills add inngest/inngest-skills --skill inngest-flow-control -a gemini-cli2Platform CLI
gemini skills install https://github.com/inngest/inngest-skills --path skills/inngest-flow-controlManually: put the files in place
.devin/skills/inngest-flow-control/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add inngest/inngest-skills --skill inngest-flow-control -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about inngest-flow-control
How do I install inngest-flow-control in Claude?
Run npx skills add inngest/inngest-skills --skill inngest-flow-control -a claude-code. The skill lands in ~/.claude/skills/inngest-flow-control/SKILL.md.
What does inngest-flow-control do?
It documents Inngest flow control — keyed concurrency, throttling, rate limiting, debounce, priority, singleton and event batching — and tells you which one fits a given problem.
Which language are the examples in?
TypeScript. For Python and Go the skill points to the Inngest documentation: the concepts carry over, the syntax does not.
Source text
SKILL.md · Apache-2.0
---
name: inngest-flow-control
description: "Use when handling external API rate limits (e.g., OpenAI 429s, HubSpot or Stripe rate limits), preventing duplicate work from rapid event bursts (debouncing user actions), spreading load over time, ensuring per-tenant fairness, processing events in batches, limiting concurrent runs of the same operation, or assigning priority to important runs. Covers Inngest flow control: concurrency limits with keys, throttling, rate limiting, debounce, priority, singleton, and event batching."
---
# Inngest Flow Control
Master Inngest flow control mechanisms to manage resources, prevent overloading systems, and ensure application reliability. This skill covers all flow control options with prescriptive guidance on when and how to use each.
> **These skills are focused on TypeScript.** For Python or Go, refer to the [Inngest documentation](https://www.inngest.com/llms.txt) for language-specific guidance. Core concepts apply across all languages.
## Quick Decision Guide
- **"Limit how many run at once"** → Concurrency
- **"Spread runs over time"** → Throttling
- **"Block after N runs in a period"** → Rate Limiting
- **"Wait for activity to stop, then run once"** → Debounce
- **"Only one run at a time for this key"** → Singleton
- **"Process events in groups"** → Batching
- **"Some runs are more important"** → Priority
## Concurrency
**When to use:** Limit the number of executing steps (not function runs) to manage computing resources and prevent system overwhelm.
**Key insight:** Concurrency limits active code execution, not function runs. A function waiting on `step.sleep()` or `step.waitForEvent()` doesn't count against the limit.
### Basic Concurrency
```typescript
inngest.createFunction(
{
id: "process-images",
concurrency: 5,
triggers: [{ event: "media/image.uploaded" }]
},
async ({ event, step }) => {
// Only 5 steps can execute simultaneously
await step.run("resize", () => resizeImage(event.data.imageUrl));
}
);
```
### Concurrency with Keys (Multi-tenant)
Use `key` parameter to apply limit per unique value of the key.
```typescript
inngest.createFunction(
{
id: "user-sync",
concurrency: [
{
key: "event.data.user_id",
limit: 1
}
],
triggers: [{ event: "user/profile.updated" }]
},
async ({ event, step }) => {
// Only 1 step per user can execute at once
// Prevents race conditions in user-specific operations
}
);
```
### Account-level Shared Limits
```typescript
inngest.createFunction(
{
id: "ai-summary",
concurrency: [
{
scope: "account",
key: `"openai"`,
limit: 60
}
],
triggers: [{ event: "ai/summary.requested" }]
},
async ({ event, step }) => {
// Share 60 concurrent OpenAI calls across all functions
}
);
```
**When to use each:**
- Basic: Protect databases or limit general capacity
- Keyed: Multi-tenant fairness, prevent "noisy neighbor" issues
- Account-level: Share quotas across multiple functions (API limits)
## Throttling
**When to use:** Control the rate of function starts over time to work around API rate limits or smooth traffic spikes.
**Key difference from concurrency:** Throttling limits function run starts; concurrency limits step execution.
```typescript
inngest.createFunction(
{
id: "sync-crm-data",
throttle: {
limit: 10, // 10 function starts
period: "60s", // per minute
burst: 5, // plus 5 immediate bursts
key: "event.data.customer_id" // per customer
},
triggers: [{ event: "crm/contact.updated" }]
},
async ({ event, step }) => {
// Respects CRM API rate limits: 10 calls/min per customer
await step.run("sync", () => crmApi.updateContact(event.data));
}
);
```
**Configuration:**
- `limit`: Functions that can start per period
- `period`: Time window (1s to 7d)
- `burst`: Extra immediate starts allowed
- `key`: Apply limits per unique key value
## Rate Limiting
**When to use:** Hard limit to prevent abuse or skip excessive duplicate events.
**Key difference from throttling:** Rate limiting discards events; throttling delays them.
```typescript
inngest.createFunction(
{
id: "webhook-processor",
rateLimit: {
limit: 1,
period: "4h",
key: "event.data.webhook_id"
},
triggers: [{ event: "webhook/data.received" }]
},
async ({ event, step }) => {
// Process each webhook only once per 4 hours
// Prevents duplicate webhook spam
}
);
```
**Use cases:**
- Prevent webhook duplicates
- Limit expensive operations per user
- Protection against abuse
## Debounce
**When to use:** Wait for a series of events to stop arriving before processing the latest one.
```typescript
inngest.createFunction(
{
id: "save-document",
debounce: {
period: "5m", // Wait 5min after last edit
key: "event.data.document_id",
timeout: "30m" // Force save after 30min max
},
triggers: [{ event: "document/content.changed" }]
},
async ({ event, step }) => {
// Saves document only after user stops editing
// Uses the LAST event received
await step.run("save", () => saveDocument(event.data));
}
);
```
**Perfect for:**
- User input that changes rapidly (search, document editing)
- Noisy webhook events
- Ensuring latest data is processed
## Priority
**When to use:** Execute some function runs ahead of others based on dynamic data.
```typescript
inngest.createFunction(
{
id: "process-order",
priority: {
// VIP users get priority up to 120 seconds ahead
run: "event.data.user_tier == 'vip' ? 120 : 0"
},
triggers: [{ event: "order/placed" }]
},
async ({ event, step }) => {
// VIP orders jump ahead in the queue
}
);
```
**Advanced example:**
```typescript
inngest.createFunction(
{
id: "support-ticket",
priority: {
run: `
event.data.severity == 'critical' ? 300 :
event.data.severity == 'high' ? 120 :
event.data.user_plan == 'enterprise' ? 60 : 0
`
},
triggers: [{ event: "support/ticket.created" }]
},
async ({ event, step }) => {
// Critical tickets get highest priority (300s ahead)
// High severity: 120s ahead
// Enterprise users: 60s ahead
// Everyone else: normal priority
}
);
```
## Singleton
**When to use:** Ensure only one instance of a function runs at a time.
### Skip Mode (Preserve Current Run)
```typescript
inngest.createFunction(
{
id: "data-backup",
singleton: {
key: "event.data.database_id",
mode: "skip"
},
triggers: [{ event: "backup/requested" }]
},
async ({ event, step }) => {
// Skip new backups if one is already running for this database
await step.run("backup", () => performBackup(event.data.database_id));
}
);
```
### Cancel Mode (Use Latest Event)
```typescript
inngest.createFunction(
{
id: "realtime-sync",
singleton: {
key: "event.data.user_id",
mode: "cancel"
},
triggers: [{ event: "user/data.changed" }]
},
async ({ event, step }) => {
// Cancel previous sync and start with latest data
await step.run("sync", () => syncUserData(event.data));
}
);
```
## Batching
**When to use:** Process multiple events together for efficiency.
```typescript
inngest.createFunction(
{
id: "bulk-email-send",
batchEvents: {
maxSize: 100, // Up to 100 events
timeout: "30s", // Or 30 seconds, whichever first
// `key` groups events into separate batches per unique value
// This is different from expressions `if` which filters events
key: "event.data.campaign_id" // Batch per campaign
},
triggers: [{ event: "email/send.queued" }]
},
async ({ events, step }) => {
// Process array of events together
const emails = events.map((evt) => ({
to: evt.data.email,
subject: evt.data.subject,
body: evt.data.body
}));
await step.run("send-batch", () => emailService.sendBulk(emails));
}
);
```
## Combining Flow Control
### Example: Fair AI Processing
```typescript
inngest.createFunction(
{
id: "ai-image-processing",
// Global throttling for API limits
throttle: {
limit: 50,
period: "60s",
key: `"gpu-cluster"`
},
// Per-user concurrency for fairness
concurrency: [
{
key: "event.data.user_id",
limit: 3
}
],
// VIP users get priority
priority: {
run: "event.data.plan == 'pro' ? 60 : 0"
},
triggers: [{ event: "ai/image.generate" }]
},
async ({ event, step }) => {
// Combines multiple flow controls for optimal resource usage
}
);
```
**Pro tip:** Most production functions benefit from combining 1-3 flow control mechanisms for optimal reliability and performance.
© inngest · Apache-2.0 · inngest/inngest-skills