Build serverless event-driven workflows
inngestskillsetup L3★0
Sheshiyer/skill-clusters ↗What it does
Build event-driven durable background jobs serverless
Best for
When implementing serverless background jobs and durable multi-step workflows without queue infrastructure
Inputs
- · Event schema, step definitions, concurrency limits, retry policy
Outputs
- · Inngest function, deployed to Vercel/Netlify/Fly/Railway
Requires
- · Inngest CLI (inngest-cli)
- · HTTP-compatible runtime (Next.js, Express, Hono, Remix, SvelteKit)
- · Vercel or Cloudflare or Netlify or Railway or Fly.io
Preconditions
- · Runtime HTTP framework installed
- · Inngest account and API key
- · Functions have unique IDs
Failure modes
- · Function not registered with serve()
- · Event not defined in schema
- · Concurrency limit hit without backoff
- · Idempotency key collision
- · Fan-out event race condition
- · Sleep duration syntax error (must use strings like '24h', '15m')
Trust signals
- · Step results durably stored
- · Built-in exponential backoff on retries
- · Concurrency as first-class concern (with limits)
- · Idempotency keys prevent duplicates
- · Sleep is non-blocking (not polling)
- · Fan-out pattern with step.sendEvent()