inngest-steps

Use step.sleep with a duration string like "24h" or "7d", or step.sleepUntil with a specific Date. The function pauses without consuming compute and resumes durably even if the process restarts.

step.waitForEvent matches events by name with optional CEL expressions and suits cases where multiple functions may handle the same event. step.waitForSignal targets a unique signal string for exact 1:1 matching with a specific function run.

Code outside steps re-executes every time a step runs because each step is a separate HTTP request. Move all non-deterministic logic like API calls, database queries, and logging inside step.run blocks.

No, waitForEvent only catches events sent after that step executes. Always handle the null return value, which indicates the timeout elapsed without a matching event arriving.

Each function allows a maximum of 1,000 steps, 4MB per step output, and 32MB total per function run. Step IDs can be reused in loops since Inngest handles counters automatically.

Create step.run promises without awaiting, then await them together with Promise.all. In v4, parallel execution is optimized by default; use group.parallel for true Promise.race semantics since plain race waits for all promises to settle.