inngest-steps

Orchestrate durable Inngest background workflows with retriable steps.

1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/YOYOMAII/foundry --skill inngest-steps-yoyomaii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inngest-steps
Source: https://github.com/YOYOMAII/foundry/tree/main/.agents/skills/inngest-steps
Command: npx skills add https://github.com/YOYOMAII/foundry --skill inngest-steps-yoyomaii

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires inngest.

What problem does it solve?

This skill solves the challenge of building reliable, long-running background processes that must survive server restarts, crashes, or network failures without losing state.

Core Features & Use Cases

  • Durable Execution: Automatically checkpoints function progress, allowing for independent retries of individual steps.
  • Workflow Orchestration: Provides primitives for delays, event-driven triggers, parallel execution, and function composition.
  • Use Case: Implement a complex onboarding flow that requires waiting for a user to click an email link (waitForEvent), sleeping for 24 hours (step.sleep), and then triggering a CRM update (step.run) without risking data loss if the server restarts.

Quick Start

Use the inngest-steps skill to implement a durable workflow function that executes a series of retriable steps with a 24-hour delay between them.

Frequently Asked Questions about inngest-steps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build durable workflows in TypeScript that survive server restarts?

Durable workflows in TypeScript survive server restarts by using Inngest step primitives to automatically checkpoint function progress. This allows individual workflow steps to retry independently after crashes or network failures without losing execution state.

What is the best way to orchestrate event-driven synchronization with long delays in background jobs?

Event-driven synchronization in background jobs is best handled through workflow orchestration primitives that manage long-duration sleeps and waitForEvent triggers. This coordinates parallel execution and reliable state management across complex asynchronous operations without data loss.

Does Inngest support fault-tolerant execution for complex onboarding flows?

Inngest supports fault-tolerant execution for complex onboarding flows by orchestrating durable, stateful background workflows. It handles waiting for email link clicks, implements 24-hour sleeps, and triggers CRM updates with automatic retries to prevent data loss during failures.

How do I implement parallel processing and retries in an event-driven architecture?

Parallel processing and retries in an event-driven architecture are implemented using durable execution step primitives that checkpoint function progress. This allows independent retries of failed steps and coordinates parallel task execution within reliable state management workflows.

When should I use durable execution for background processing instead of standard asynchronous tasks?

Durable execution should be used for background processing when tasks require surviving server restarts, crashes, or network failures. Standard asynchronous tasks lack the checkpointed state management needed for long-duration sleeps, event-driven synchronization, and reliable parallel processing.