> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/create-and-publish/publishing-and-distribution/get-notified-when-an-episode-goes-live.md).

# Get notified when an episode goes live

Understand the email, browser, mobile app, and in-app notifications for a published or failed episode.

When you publish or schedule an episode, Podigee encodes the audio and then puts the episode live. You do not have to wait in the browser. Podigee tells you by email, by a browser notification, in the Podigee mobile app, or in the notifications panel of the Podigee workspace.

## How it works

* In the publish dialog, **Notify me of publication by** sets the channel for this episode: no notification, a browser notification, an email, or both. Select **Save as default settings** to keep the choice for future episodes. On current plans, **Publish now** always sends the email.
* The email and the browser notification go to the person who started the publication, or to the podcast owner when the publication was started in another way.
* Episodes that arrive through a podcast import send no notification of their own.

{% tabs %}
{% tab title="Classic view" %}

### Email

When the episode is live, the email **"\[episode title]" from "\[podcast title]" is live** arrives with links to the episode, the analytics, the exports, and the public episode page.

When the publication fails, the email **"\[episode title]" was not published** arrives. It states that the episode is not live and that listeners did not receive it, and names the scheduled date when there was one. Podigee sends this email independent of the chosen channel.

### Browser notification

The browser notification appears on the device where you allowed notifications for Podigee. When the browser blocks them, the publish dialog shows **Notifications of this type are blocked for this site**. Allow notifications for the Podigee site in the browser settings.

### Mobile app

The Podigee mobile app for Android and iOS receives push notifications for these events:

| Event                | Notification                                                                                    |
| -------------------- | ----------------------------------------------------------------------------------------------- |
| Episode published    | **Episode published**: the episode for your podcast has been published                          |
| Encoding failed      | **Encoding failed**                                                                             |
| Milestone reached    | Download milestones such as your first 100, 250, or 500 downloads, and published-episode counts |
| Product announcement | News from Podigee                                                                               |

The classic view does not show milestones. You see them in the mobile app and in the notifications panel of the Podigee workspace. The milestone notification does not arrive at the moment when the download count is reached.

### Example

You schedule an episode for 06:00 and choose email and browser notification. At 06:00 the episode goes live in the feed. Shortly after, the email arrives, and the browser on your desk shows the notification. If you also use the mobile app, the app shows **Episode published**.

### Important decisions

* Choose the email when you schedule episodes for a time when you are not at the computer.
* Choose the browser notification when you publish while you work in Podigee.
* Remember the error email. It always arrives, and it is the signal to open the episode and check the media.
  {% endtab %}

{% tab title="Podigee workspace" %}

### Notifications panel

The bell in the top bar opens the **Notifications** panel. The bell is on every page of the Podigee workspace, also in the Recording Studio. The panel lists the news about your shows and the Podigee updates in one list. The newest entry is at the top, and the entries are grouped by day.

| Event                     | Entry in the panel                                                                      |
| ------------------------- | --------------------------------------------------------------------------------------- |
| Episode is live           | **"\[episode title]" is live**                                                          |
| Episode was not published | **"\[episode title]" was not published**, with the button **Replace recording**         |
| Recording is ready        | **Your recording "\[title]" is ready**                                                  |
| Import finished           | **\[show] was imported: \[number] episodes**                                            |
| Import failed             | **The import of \[show] failed**, with the button **Open import**                       |
| Milestone reached         | **\[show] reached \[number] downloads** or **\[show] has \[number] published episodes** |

* Select an entry about your shows to open the page that it is about. A milestone opens the analytics of the show.
* An entry for an episode that was not published stays at the top of the panel until the episode is published. An entry for a failed import stays at the top while the import is still failed.
* The badge on the bell counts the new entries. It shows **9+** for more than nine. The badge goes away when you open the panel.
* An entry about your shows stays unread until you select it or select **Mark all as read**.
* News about a show goes to the owner of the show, also when another person started the publication.
* Import entries are for imports that you start in the Podigee workspace.
* News about your shows stays in the panel for 90 days. This also applies to an entry at the top: after 90 days it leaves the panel, also when the episode or the import still has the problem. The panel does not show events from before the panel was introduced.

The panel is in addition to the email and the mobile app. Podigee still sends them as before.

### Choose the channel

The Podigee workspace does not include a notification choice in the publish step yet. Switch to the classic view to choose how Podigee notifies you by email or in the browser.
{% endtab %}
{% endtabs %}

## Related tasks

* [Schedule or change an episode publication](https://docs.podigee.com/documentation/create-and-publish/production/episodes/schedule-or-change-an-episode-publication.md)
* [Understand your RSS feed](https://docs.podigee.com/documentation/create-and-publish/publishing-and-distribution/understand-your-rss-feed.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://docs.podigee.com/documentation/create-and-publish/publishing-and-distribution/get-notified-when-an-episode-goes-live.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.
