high severityInngest function execution/replay
Throttled functions (concurrency=1 per tenant/environment) execute later events (e.g., booking) before earlier ones (e.g., customer upsert) complete, even while the earlier is retrying on failure, leading to out-of-order processing.
Root cause
Independent functions triggered by separate events process concurrently despite per-function concurrency limits; retries do not block subsequent functions from dequeuing and executing out of order.
Inngestconcurrencyreplayorderingthrottlingevent-driven