inngest-steps

You orchestrate durable workflows using Inngest steps like step.run and step.sleep to enforce deterministic, retryable execution that survives process restarts and failures. This pattern handles long-running tasks and event-driven processes reliably.

You implement human-in-the-loop approvals using step.waitForEvent or step.waitForSignal to pause durable workflow execution until manual input is received. This maintains process state without blocking serverless resources during the wait.

You run parallel steps by composing multiple step.run calls concurrently, and apply chunking or batching strategies for large datasets. You can also reuse step IDs in loops to create automatic counters for iterative processing within durable workflows.

Yes, you use step.invoke and step.sendEvent for cross-service orchestration in TypeScript. These methods allow durable workflows to trigger external functions and emit events across services while maintaining step-level isolation and reliability.

Workflow steps may appear to re-execute after a serverless restart if deterministic execution is not enforced. By using step.run with unique step IDs, Inngest tracks completed operations and skips them during replays, ensuring only uncompleted steps are retried.