Routing Rules and Execution Model

A routing connects one inbox to one integration and controls message forwarding.

Execution model

1. Message arrives in an inbox.
2. Active routings for that inbox are loaded.
3. Matching routings create delivery jobs.
4. Deliveries run with integration-specific behavior and retry policy.

Good routing design

Keep names explicit

Use names that identify source + destination + purpose.

Start narrow, then expand

Begin with one routing for a new integration and scale once validated.

Audit inactive rules

Inactive routings are safe to keep for rollback, but stale rules should be documented.

Related

• Create First Routing
• Choosing Integration Types by Use Case