---
title: "Reconnecting – Full" / "Reconnecting – Rejected" on a stream
slug: troubleshooting/reconnecting-full-reconnecting-rejected-on-a-stream
docTags: 
createdAt: 2025-04-30T21:21:12.416Z
---

### ERROR

Error "Reconnecting - Full Full" on a stream input or output

![](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/bXaUMHzsWfCik6ju-fK5U_reconneting.png)

### ISSUE

A stream (input or output) stays in a **Reconnecting** state with an error of **Full** or **Rejected**. These look similar but have different causes — the error field tells you which:

**"Full"** — the remote Broadcaster refused the connection because it is **at capacity or has hit a configured limit** (e.g. server full, or a max sources / max outputs / object limit reached). The connecting side keeps retrying, so the stream cycles in *Reconnecting – Full*.

**"Rejected"** — the stream is **already connected somewhere else**: another feeder/Broadcaster/decoder is using the same stream ID. The two ends repeatedly displace each other, so the output keeps disconnecting and reconnecting.

### RESOLUTION

- **Full:** free up capacity on the target Broadcaster, raise the relevant limit (max sources/outputs), or connect to a different Broadcaster.
- **Rejected:** find and stop the duplicate feeder/decoder using the same stream ID so only one end is connected.