> For the complete documentation index, see [llms.txt](https://guide.prismlive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.prismlive.com/desktop/guides/error-solution/naver-shopping-error/how-to-fix-forced-broadcast-termination-errors.md).

# How to Fix Forced Broadcast Termination Errors

Windows, Mac

A broadcast may be forcibly terminated when a termination signal is received from the Naver Shopping Live server via MQTT. This error is not caused by PRISM Live Studio.

***

### Broadcast Forcibly Terminated

{% hint style="danger" %}
Error Message: Shopping Live was terminated due to a problem with the broadcast. For more information, contact NAVER Shopping Live. (Error code: 30026)
{% endhint %}

#### Cause

A broadcast termination MQTT message was received from the Naver Shopping Live server, causing the broadcast to be forcibly ended. This is not an error originating from PRISM Live Studio. It occurs when the Naver Shopping Live service sends a termination signal to the broadcast.

#### Solution

1. Contact NAVER Shopping LIVE support to confirm the reason for the forced termination.
2. When submitting your inquiry, providing the approximate time the termination occurred and your broadcast details will help speed up the investigation.

<br>

[Desktop](/desktop/overview.md), [Guides](/desktop/guides.md), [Error Solution](/desktop/guides/error-solution.md), [Naver Shopping Error](/desktop/guides/error-solution/naver-shopping-error.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guide.prismlive.com/desktop/guides/error-solution/naver-shopping-error/how-to-fix-forced-broadcast-termination-errors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.