Subscriptions & filters
A subscription links a destination to one or more event-type patterns. The realtime outbound engine matches each committed event against active subscriptions for the fork, then enqueues a delivery job per match.
Patterns
| Pattern | Matches |
|---|---|
* | All event types |
order.* | order.created, order.shipped, … |
payment.captured | Exact type only |
Patterns are evaluated against the internal event type string (exported to customers as body field type / header causet-event-type). Prefer narrow patterns in production — * is useful for debugging and mirroring.
Lifecycle
| State | Behavior |
|---|---|
| Active | Jobs are created and dispatched |
| Paused (destination or subscription) | Matching stops or dispatch pauses — see UI |
| Deleted | No new jobs; in-flight jobs finish or fail per policy |
Config changes are versioned. The data plane loads the active config for the fork so runtime never needs customer credentials.
Fan-out
One committed event can match multiple subscriptions (e.g. Kafka + webhook). Each match gets its own delivery job and Delivery Log row — failures on one adapter do not roll back the ledger commit or other destinations.