---
title: "Fan-Out to Multiple Destinations"
description: "Deliver a single SAP document to multiple destinations in parallel."
---

# Fan-Out to Multiple Destinations

Fan-out delivers one SAP document — from ArchiveLink, CMIS, or OData — to multiple destinations in parallel. It's not a feature you enable; it's the natural result of wiring **multiple connections from the same source**.

```
                            ┌──> Connection 1 ──> S3 Bucket (archive)
Source (SAP repo Z1) ───────┼──> Connection 2 ──> SharePoint (team access)
                            └──> Connection 3 ──> Email (notification)
```

Each connection is independent. Delivery to one destination does not wait on the others.

## Typical patterns

**Archive + share + notify**

| Destination | Purpose |
|---|---|
| Amazon S3 | Long-term archival with lifecycle policies |
| SharePoint | Team review + collaboration |
| Email | Notification to the responsible team |

**Multi-region archiving**

| Destination | Purpose |
|---|---|
| S3 (us-east-1) | Primary archive (US) |
| S3 (eu-west-1) | Compliance copy (EU) |
| Azure Blob (UK) | Secondary archive (UK) |

**Dev/test mirror** — production source → both prod and dev destinations.

## Independent delivery tracking

Each destination has its own status. A document can be `delivered` to S3 while `retrying` for SharePoint — failure at one doesn't block the others. Each destination retries on its own under the workspace retry policy.

The Documents page shows per-destination status on expand.

> **REPLACE:** Screenshot of per-destination delivery status

## Partial failure semantics

- **Successful deliveries are final** — no rollback at destinations that already received the document.
- **Failed deliveries retry** per the workspace [retry policy](/docs/workspaces/settings).
- **Retries are per-destination** — a SharePoint retry doesn't re-send to S3.
- **Exhausted retries** → the failed action setting decides (mark failed / discard).

You never lose a document at one destination because of a failure at another. The delivery guarantee is per-destination, not all-or-nothing.

Filter on the Documents page for any-failed-destination to triage.

## Configure

1. **Connections** page.
2. Connect your source to the first destination.
3. Another connection from the same source to the next destination.
4. Repeat.

Each connection can have its own [routing](/docs/connections/routing) — different subfolders and naming per destination.

## Performance

Fan-out is parallel — adding destinations doesn't slow the SAP-side response (especially in buffer mode). Each destination is a separate delivery to monitor, and the workspace retry policy applies uniformly.

## Limits

No hard cap on destinations per workspace or connections per source — fan out to as many as you need. Practical limits = your deployment's licensed scope and the throughput of each destination.

## Next steps

- [Connections Overview](/docs/connections/overview)
- [Document Routing](/docs/connections/routing)
- [Workspace Settings](/docs/workspaces/settings)