inngest-events

Set a unique id field on the event, such as invoice-paid-${invoiceId}, and Inngest deduplicates events with the same id within a 24-hour window. Use IDs specific to the event type and instance rather than generic values like a customer ID.

Send a single event like user/signup.completed and create multiple functions that each trigger on that same event. Each function runs independently and in parallel, so one failure does not affect the others, and failed functions can be replayed selectively.

Use the object-action pattern domain/noun.verb in past tense, such as billing/invoice.paid or user/profile.updated. Use dots for hierarchy, optional prefixes for grouping like stripe/customer.created, and avoid underscores or vague names.

Yes, set the ts parameter to a future Unix timestamp in milliseconds and Inngest delays delivery until that time. The ts field also maintains chronological ordering when sending batches of related events.

Create a function triggered by the inngest/function.failed system event, which provides function_id, run_id, and error details in event.data. Use it to log failures, send alerts for critical functions, or schedule automatic retries.

The skill's code examples are TypeScript-focused, but core concepts like event schema, idempotency IDs, and fan-out apply across languages. For Python or Go syntax, refer to the official Inngest documentation.