inngest-jobs

Implement durable background job execution with idempotency and retries.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill inngest-jobs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inngest-jobs
Source: https://github.com/robotijn/ctoc/tree/main/skills/saas/inngest-jobs
Command: npx skills add https://github.com/robotijn/ctoc --skill inngest-jobs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of unreliable background job execution in SaaS applications, preventing duplicate side effects, lost events, and failed retries that break critical user-facing workflows like dunning emails, scheduled reports, and async post-processing.

Core Features & Use Cases

  • Durable event-driven execution: Build background jobs that survive server crashes and retries without duplicate side effects, using step boundaries to memoize successful operations.
  • Built-in resilience guardrails: Automatic retries with backoff, idempotency keys, per-tenant concurrency limits, and dead-letter handling for failed or "poison" jobs.
  • Multi-engine and multi-stack support: Works with Inngest, Temporal, Trigger.dev, and other durable execution engines for Next.js, Hono, Bun, FastAPI, .NET, and Spring SaaS stacks.
  • Real-world use case: Set up a dunning email workflow that sends payment reminders 10 minutes after a failed charge, with no duplicate emails even if the job crashes mid-execution.

Quick Start

Use the inngest-jobs skill to set up a durable background job that sends a welcome email to new users, with automatic retries and no duplicate sends if the job crashes mid-execution.

Frequently Asked Questions about inngest-jobs

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

FAQPage Schema
How do I prevent duplicate side effects in background jobs after a server crash?

Durable event-driven background jobs prevent duplicate side effects by enforcing idempotency at step boundaries, which memoizes successful operations so crashed retries skip previously completed steps.

Does this background job execution approach support FastAPI and Next.js stacks?

Yes, durable event-driven background job execution supports FastAPI, Next.js, Hono, Bun, .NET, and Spring SaaS stacks, integrating with engines like Inngest, Temporal, and Trigger.dev.

How do I set up a dunning email workflow with automatic retries and no duplicate sends?

Set up a durable background job that sends payment reminders after a failed charge, using automatic retries with backoff and idempotency keys to ensure no duplicate emails are sent during crashes.

What is the best way to handle poison messages in event-driven SaaS workflows?

Handle poison messages in event-driven SaaS workflows by using built-in dead-letter handling, which isolates failed jobs that exhaust retries, preventing them from blocking per-tenant concurrency limits.

Why do I need the outbox pattern for reliable database-to-queue event handoff?

The outbox pattern ensures reliable database-to-queue event handoff by atomically recording events in your DB before dispatching them, preventing lost events when integrating durable execution engines.