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 your process restarts.

step.waitForEvent matches events by name and optional CEL expressions, suited when 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 completes 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 set a timeout and check for a null return, which indicates the event never arrived within the window.

Use step.invoke with an imported function reference and a data payload; the result is fully typed. For cross-app calls, use referenceFunction with the appId and functionId, since string function IDs are no longer supported in v4.

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