inngest-events

Set a unique id field on each event, such as `invoice-paid-${invoiceId}`, specific to the event type and instance. Inngest deduplicates events with the same ID within a 24-hour window from first reception, which handles at-least-once delivery from sources like Stripe.

Use the object-action pattern: `domain/noun.verb` in past tense, like `billing/invoice.paid` or `user/profile.updated`. Use dots for hierarchy, add prefixes to group related events, and avoid underscores or vague names like `payment`.

Use the fan-out pattern: send one event and create multiple functions that each list that event in their triggers. Each function runs independently and in parallel, so one failure does not affect the others, and you can replay only failed functions.

Yes, set the ts parameter to a future Unix timestamp in milliseconds when calling inngest.send. The event is delivered at that time, which is useful for trial reminders or delayed retries, and timestamps also maintain chronological ordering.

The skill content is focused on TypeScript. Core concepts like event schemas, idempotency, and fan-out apply across languages, but for Python or Go syntax you should refer to the official Inngest documentation.

Create a function triggered by the `inngest/function.failed` system event. Its event data includes function_id, run_id, and error details, which you can use to log failures, send alerts for critical functions, or schedule automatic retries.