@inngest

inngest-flow-control covers concurrency limits, throttling, rate limiting, debounce, priority, singleton, and event batching patterns. a quick decision guide maps problem statements to control mechanisms, though implementation procedures remain incomplete.

Use when adding durable execution to a TypeScript project — building retry-safe webhook handlers, background jobs that survive crashes, scheduled tasks, or…

Use when building functions that must survive process crashes, retry automatically on failure, run on a schedule, react to events, or maintain state across…

Use when implementing delays that must survive process restarts (e.g., 24-hour cart abandonment, scheduled follow-ups), waiting for human approval or external…

Use when designing event-driven workflows, decoupling services, implementing fan-out patterns (one trigger, many downstream handlers), implementing idempotent…

Use when adding cross-cutting concerns to durable functions — structured logging or tracing across all functions, error tracking with Sentry, payload…