From 288f9966ad31b7c46f86d8ff507f48fd448b730f Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Tue, 23 Jun 2026 05:32:51 +0000 Subject: [PATCH 1/7] docs: document tokenId-scoped restream dedup behavior Co-Authored-By: zita.liao --- millicast/distribution/re-streaming.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/millicast/distribution/re-streaming.mdx b/millicast/distribution/re-streaming.mdx index ae8c29eec229..a94f2e6a504c 100644 --- a/millicast/distribution/re-streaming.mdx +++ b/millicast/distribution/re-streaming.mdx @@ -76,6 +76,14 @@ For scenarios such as [Multi-Source Broadcasting](/millicast/broadcast/multi-sou To disable re-streaming on specific feeds add the **norestream** boolean [publishing parameter](/millicast/broadcast/publishing-parameters.md) to your configured publishing URLs. This is used to indicate which sources specifically should be used or not. For example, in a Multi-bitrate (MBR) configuration where there are multiple quality layers being ingested, you might re-stream only the highest quality layer and then add `&norestream` to any additional contribution layers. Similarly, if you have an interactive [multi-view](/millicast/playback/multi-view.md) broadcast where multiple sources are sharing the same publishing token, you can configure the URLs to only re-stream your intended source. +:::info Token-scoped dedup behavior +Re-streaming is deduplicated **per publish token on each publisher node**. Only one stream per publish token can actively re-stream on a given node at a time. If a new feed starts publishing with the same token that is already re-streaming, the existing re-stream is stopped and the new feed takes over. + +This means that when multiple streams share the same publish token, only the most recently connected feed will re-stream. To prevent this, add `&norestream` to the publishing URLs of any feeds that should not re-stream. + +Note that this dedup is **node-local** — if feeds using the same token connect to different publisher nodes, each node will independently re-stream its feed, which may result in duplicate re-streams to the same destination. +::: + ## Feature compatibility ### Cloud transcoder and Re-streaming From 00e5e919df30ebdd33affb0b853feecef277526b Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Tue, 23 Jun 2026 06:20:15 +0000 Subject: [PATCH 2/7] =?UTF-8?q?docs:=20address=20review=20=E2=80=94=20rewr?= =?UTF-8?q?ite=20as=20user-facing=20section,=20remove=20internal=20termino?= =?UTF-8?q?logy?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: zita.liao --- millicast/distribution/re-streaming.mdx | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/millicast/distribution/re-streaming.mdx b/millicast/distribution/re-streaming.mdx index a94f2e6a504c..83ef26768629 100644 --- a/millicast/distribution/re-streaming.mdx +++ b/millicast/distribution/re-streaming.mdx @@ -76,13 +76,11 @@ For scenarios such as [Multi-Source Broadcasting](/millicast/broadcast/multi-sou To disable re-streaming on specific feeds add the **norestream** boolean [publishing parameter](/millicast/broadcast/publishing-parameters.md) to your configured publishing URLs. This is used to indicate which sources specifically should be used or not. For example, in a Multi-bitrate (MBR) configuration where there are multiple quality layers being ingested, you might re-stream only the highest quality layer and then add `&norestream` to any additional contribution layers. Similarly, if you have an interactive [multi-view](/millicast/playback/multi-view.md) broadcast where multiple sources are sharing the same publishing token, you can configure the URLs to only re-stream your intended source. -:::info Token-scoped dedup behavior -Re-streaming is deduplicated **per publish token on each publisher node**. Only one stream per publish token can actively re-stream on a given node at a time. If a new feed starts publishing with the same token that is already re-streaming, the existing re-stream is stopped and the new feed takes over. +## Re-streaming scope per publish token -This means that when multiple streams share the same publish token, only the most recently connected feed will re-stream. To prevent this, add `&norestream` to the publishing URLs of any feeds that should not re-stream. +Re-streaming is scoped to the **publish token**. Only one active ingest per publish token will be re-streamed at a time. If a new ingest starts using the same publish token while another is already re-streaming, the existing re-stream is stopped and the new ingest takes over. -Note that this dedup is **node-local** — if feeds using the same token connect to different publisher nodes, each node will independently re-stream its feed, which may result in duplicate re-streams to the same destination. -::: +To re-stream different ingests independently, use a **separate publish token** for each ingest. If multiple ingests must share the same publish token, add `&norestream` to the publishing URLs of any ingests that should not re-stream. ## Feature compatibility From 66e70df5c624307ab28df4ec2fae27bbe1035f7f Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Tue, 23 Jun 2026 07:28:45 +0000 Subject: [PATCH 3/7] docs: soften restream dedup wording, recommend separate tokens Co-Authored-By: zita.liao --- millicast/distribution/re-streaming.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/millicast/distribution/re-streaming.mdx b/millicast/distribution/re-streaming.mdx index 83ef26768629..9dbe823abc8c 100644 --- a/millicast/distribution/re-streaming.mdx +++ b/millicast/distribution/re-streaming.mdx @@ -78,7 +78,7 @@ To disable re-streaming on specific feeds add the **norestream** boolean [publis ## Re-streaming scope per publish token -Re-streaming is scoped to the **publish token**. Only one active ingest per publish token will be re-streamed at a time. If a new ingest starts using the same publish token while another is already re-streaming, the existing re-stream is stopped and the new ingest takes over. +Re-streaming is scoped to the **publish token**. Only one active ingest per publish token will be re-streamed at a time. If a new ingest starts using the same publish token while another is already re-streaming, the existing re-stream would be stopped and replaced by the new ingest. Because of this, **re-streaming multiple ingests with the same publish token is not recommended** — the behavior may be unpredictable. To re-stream different ingests independently, use a **separate publish token** for each ingest. If multiple ingests must share the same publish token, add `&norestream` to the publishing URLs of any ingests that should not re-stream. From db4044738969684ef4ae27077ce0e42002e1fc4d Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Thu, 25 Jun 2026 01:24:11 +0000 Subject: [PATCH 4/7] =?UTF-8?q?docs:=20rewrite=20restream=20token=20scope?= =?UTF-8?q?=20=E2=80=94=20undefined=20behavior,=20not=20supported?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: zita.liao --- millicast/distribution/re-streaming.mdx | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/millicast/distribution/re-streaming.mdx b/millicast/distribution/re-streaming.mdx index 9dbe823abc8c..bd57cefc6351 100644 --- a/millicast/distribution/re-streaming.mdx +++ b/millicast/distribution/re-streaming.mdx @@ -78,9 +78,12 @@ To disable re-streaming on specific feeds add the **norestream** boolean [publis ## Re-streaming scope per publish token -Re-streaming is scoped to the **publish token**. Only one active ingest per publish token will be re-streamed at a time. If a new ingest starts using the same publish token while another is already re-streaming, the existing re-stream would be stopped and replaced by the new ingest. Because of this, **re-streaming multiple ingests with the same publish token is not recommended** — the behavior may be unpredictable. +Re-streaming is scoped to the **publish token**. When multiple ingests share the same publish token, the system's load balancer may route them to different internal nodes, resulting in undefined behavior: -To re-stream different ingests independently, use a **separate publish token** for each ingest. If multiple ingests must share the same publish token, add `&norestream` to the publishing URLs of any ingests that should not re-stream. +- If two ingests are routed to the same node, one re-stream may be stopped and replaced by the other. +- If they are routed to different nodes, both may attempt to re-stream to the same endpoint simultaneously, causing errors or corrupted statistics at the re-stream destination. + +Because of this, **re-streaming multiple ingests with the same publish token is not supported**. To re-stream different ingests independently, use a **separate publish token** for each ingest. If multiple ingests must share the same publish token, add `&norestream` to the publishing URLs of any ingests that should not re-stream. ## Feature compatibility From 0c000f733d6ba5ee79fda2acedef4b5e6af5db0f Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Thu, 25 Jun 2026 01:51:11 +0000 Subject: [PATCH 5/7] docs: remove internal tech terms, keep undefined behavior plain Co-Authored-By: zita.liao --- millicast/distribution/re-streaming.mdx | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/millicast/distribution/re-streaming.mdx b/millicast/distribution/re-streaming.mdx index bd57cefc6351..092f71ce6600 100644 --- a/millicast/distribution/re-streaming.mdx +++ b/millicast/distribution/re-streaming.mdx @@ -78,10 +78,7 @@ To disable re-streaming on specific feeds add the **norestream** boolean [publis ## Re-streaming scope per publish token -Re-streaming is scoped to the **publish token**. When multiple ingests share the same publish token, the system's load balancer may route them to different internal nodes, resulting in undefined behavior: - -- If two ingests are routed to the same node, one re-stream may be stopped and replaced by the other. -- If they are routed to different nodes, both may attempt to re-stream to the same endpoint simultaneously, causing errors or corrupted statistics at the re-stream destination. +Re-streaming is scoped to the **publish token**. If multiple ingests share the same publish token while re-streaming is active, the behavior is undefined — the existing re-stream may be stopped, or multiple ingests may attempt to re-stream to the same endpoint simultaneously. Either case can result in errors or corrupted statistics at the re-stream destination. Because of this, **re-streaming multiple ingests with the same publish token is not supported**. To re-stream different ingests independently, use a **separate publish token** for each ingest. If multiple ingests must share the same publish token, add `&norestream` to the publishing URLs of any ingests that should not re-stream. From ef833995a3c4752f4469e1e37d26886b90fd700f Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Thu, 25 Jun 2026 02:03:22 +0000 Subject: [PATCH 6/7] docs: simplify restream token scope wording per review Co-Authored-By: zita.liao --- millicast/distribution/re-streaming.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/millicast/distribution/re-streaming.mdx b/millicast/distribution/re-streaming.mdx index 092f71ce6600..2a3a1b047f4e 100644 --- a/millicast/distribution/re-streaming.mdx +++ b/millicast/distribution/re-streaming.mdx @@ -78,9 +78,9 @@ To disable re-streaming on specific feeds add the **norestream** boolean [publis ## Re-streaming scope per publish token -Re-streaming is scoped to the **publish token**. If multiple ingests share the same publish token while re-streaming is active, the behavior is undefined — the existing re-stream may be stopped, or multiple ingests may attempt to re-stream to the same endpoint simultaneously. Either case can result in errors or corrupted statistics at the re-stream destination. +Re-streaming is scoped to the **publish token**. If a new ingest starts using the same publish token while another is already re-streaming, the behavior is unpredictable. **Re-streaming multiple ingests with the same publish token is not recommended.** -Because of this, **re-streaming multiple ingests with the same publish token is not supported**. To re-stream different ingests independently, use a **separate publish token** for each ingest. If multiple ingests must share the same publish token, add `&norestream` to the publishing URLs of any ingests that should not re-stream. +To re-stream different ingests independently, use a **separate publish token** for each ingest. If multiple ingests must share the same publish token, add `&norestream` to the publishing URLs of any ingests that should not re-stream. ## Feature compatibility From 129b2019401ec67800136fd931a8be81eb136787 Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Thu, 25 Jun 2026 02:14:53 +0000 Subject: [PATCH 7/7] docs: update restream scope wording per review Co-Authored-By: zita.liao --- millicast/distribution/re-streaming.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/millicast/distribution/re-streaming.mdx b/millicast/distribution/re-streaming.mdx index 2a3a1b047f4e..741eab84be6e 100644 --- a/millicast/distribution/re-streaming.mdx +++ b/millicast/distribution/re-streaming.mdx @@ -78,7 +78,7 @@ To disable re-streaming on specific feeds add the **norestream** boolean [publis ## Re-streaming scope per publish token -Re-streaming is scoped to the **publish token**. If a new ingest starts using the same publish token while another is already re-streaming, the behavior is unpredictable. **Re-streaming multiple ingests with the same publish token is not recommended.** +Re-streaming is scoped to the **publish token**. If multiple ingests share the same publish token while re-streaming is active, the behavior is undefined — the existing re-stream may be stopped, or multiple ingests may attempt to re-stream to the same endpoint simultaneously. Either case can result in errors or corrupted statistics at the re-stream destination. To re-stream different ingests independently, use a **separate publish token** for each ingest. If multiple ingests must share the same publish token, add `&norestream` to the publishing URLs of any ingests that should not re-stream.