> 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/mobile/guides/error-solution/youtube/the-youtube-scheduled-live-had-already-ended.md).

# The YouTube Scheduled Live Had Already Ended

{% hint style="danger" %}
The scheduled live has already ended or is no longer valid. The selected schedule will be cleared.
{% endhint %}

This guide explains the cause of the current error that occurred during your live streaming.

***

You attempted to start a live stream by selecting a scheduled broadcast registered in your YouTube Live Dashboard. However, the stream failed to start properly because the scheduled broadcast had already started and ended.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2FeJRv9fsrPuwa26IZEyi5%2Fc_4222_01.jpg?alt=media&amp;token=94c08651-7f2d-4a3f-8e09-0c61a605ac09" alt=""><figcaption></figcaption></figure>

You can check your scheduled broadcast history in the Manage menu of the YouTube Live Dashboard. Please confirm whether the scheduled broadcast you selected had already been completed.

[\[YouTube Live Dashboard\]](https://studio.youtube.com/channel/UC/livestreaming/dashboard) <br>


---

# 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/mobile/guides/error-solution/youtube/the-youtube-scheduled-live-had-already-ended.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.