inngest-handler

Build deterministic Inngest workflows with retries and event-driven waits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/alisonbessa/bluemoon --skill inngest-handler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inngest-handler
Source: https://github.com/alisonbessa/bluemoon/tree/main/.claude/skills/inngest-handler
Command: npx skills add https://github.com/alisonbessa/bluemoon --skill inngest-handler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and manage Inngest functions for reliable background jobs, workflows, and scheduled tasks.

Core Features & Use Cases

  • Deterministic steps with step.run wrapping all side effects to ensure idempotent retries.
  • Multi-step workflows and orchestration patterns using Inngest functions (e.g., sleeps, waitForEvent, parallel steps).
  • Safe error handling and rollback patterns, including onFailure handlers and automatic retries.

Quick Start

Create a minimal Inngest function that validates input, runs deterministic steps, and waits for a follow-up event.

Frequently Asked Questions about inngest-handler

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

FAQPage Schema
How do I build reliable background jobs with serverless orchestration?

Reliable serverless background jobs require durable workflows with deterministic step IDs and automatic retries. By wrapping side effects in step.run, you ensure idempotent execution and safe multi-step orchestration for complex processes.

How do I handle errors and rollbacks in multi-step workflows?

Error handling in multi-step workflows uses onFailure handlers and automatic retries to manage rollbacks safely. Separating step logic from orchestration ensures that failures trigger recovery mechanisms without corrupting the entire workflow state.

How do I wait for an event before continuing a background job?

Waiting for an event in background jobs uses the waitForEvent function within serverless orchestration. This allows workflows to pause execution deterministically until a specific follow-up event is received, resuming the next step automatically.

Why do background job retries fail with duplicate side effects?

Duplicate side effects during retries occur when non-deterministic code runs outside step.run. Enforcing deterministic step IDs and wrapping all side effects ensures idempotent retries, preventing background jobs from executing the same action twice.

Can I run parallel steps in an event-driven workflow?

Parallel steps in event-driven workflows are supported through serverless orchestration patterns. By structuring multi-step processes with distinct deterministic step IDs, you can execute concurrent side effects safely while maintaining workflow reliability.

Do I need a specific framework to use deterministic steps for background jobs?

Deterministic steps for background jobs require an orchestration layer that enforces step.run wrapping and handles event-driven waits. This approach applies to multi-step processes across various domains, independent of specific external frameworks.