Integration event routing

The Lifecycle

Transitions Explained

Routing waits for all selected consumers to handle or ignore an event. Any retry outcome schedules another numbered attempt, which may reach previously successful consumers again. The router saves unclaimed events when no eligible consumer exists; its declared failed status is not a reachable router outcome.

What Cannot Happen

A settled delivered event has no automatically scheduled next routing attempt. New consumer registration does not requeue past unclaimed events.

Concurrency and Timing

Attempt claiming prevents duplicate execution of the same routing number. Consumer calls and event-result writes are separate boundaries; a later attempt can invoke a consumer that already acted. Receiver deduplication uses the stable event identity.