Multi-destination fan-out

Where available, one accepted Event can create several independent Deliveries—one per active Destination on the Source.

Availability

Multiple active Destinations may depend on your workspace and plan. If your Source cannot add another Destination, that workspace is limited to one. Archived Destinations do not count against the active Destination allowance.

Independent Deliveries

Once an Event is accepted, each Delivery is independent:

• Destination A can return 200 while Destination B returns 500;
• B can retry while A is already delivered;
• stopping B does not stop A;
• replaying B does not resend to A;
• archiving B does not erase A's history.

Event aggregate status

A multi-destination Event has an aggregate state such as in_progress, delivered, partial, or failed. Counts are shown per Event. Open the Event to inspect each Destination's Delivery separately.

Which Destinations receive an Event

Only Destinations that are enabled and not archived receive new Events. A disabled or archived Destination does not consume new Events. Existing accepted Deliveries keep their lifecycle.

Limits

• The active Destination limit is enforced per Source and by your plan; archived Destinations do not consume an active slot.
• If an Event cannot be accepted within the Source's active Destination limit, ingestion fails rather than silently dropping a Destination.