---
title: Notices
description: Follow what your Workers did while you were away — which events raise a notice under the bell, where each opens, and which are also emailed.
new_in: "3.3"
---

A **notice** is a short message from Ysra about something one of your Workers
did while you weren’t looking: a run finished, failed or is waiting for your
approval, or an address a Worker watches went down or came back. Use notices
to know when a Worker needs you without keeping its page open. This page
covers which events raise a notice, where notices appear, and which are also
emailed; for the runs themselves, see [Runs and approvals](../workers/runs.md).

## What a notice shows

A notice names the Worker and what happened, never what the Worker read or
wrote. Every app shows the same notices, and every notice stays under the
bell whatever you choose for email.

## Where notices appear

| App | Where | Extra |
|---|---|---|
| Web app | The bell at the foot of the sidebar, named **Notices** | — |
| Desktop app | The bell at the foot of the rail, above **Help** | A new notice also shows as a system notification while the app is open and not in front; choosing it brings the app forward on that Worker |
| Phone | **Notices** in the menu | See [Notices on the phone](../mobile/index.md#notices) |

The bell shows the number of unread notices, up to “9+”. With none unread it
shows no number.

## Which events raise a notice

| When | Notice | Second line |
|---|---|---|
| A run finished | “… finished its run” | “Open it to read what it found.” |
| A run failed | “… couldn’t finish its run” | “Open it to see where it stopped and run it again.” |
| A run waits for your approval of an email | “… is waiting for your approval” | “It drafted an email. Nothing is sent until you approve the exact text.” |
| A run waits for your approval of a message | “… is waiting for your approval” | “It wants to send a message. …” |
| A watched address stopped answering | “…: the address stopped answering” | “It will keep checking and tell you when it is back.” |
| A watched address is back | “…: the address is answering again” | — |

An uptime Worker that checks every few minutes raises a notice only when the
address goes down or comes back, not for every check.

## Opening a notice

The bell opens the **Notices** panel, newest first, with unread notices
marked.

| Action | What happens |
|---|---|
| Choose a notice | It is marked read and its Worker opens. In the web app it opens on the run the notice is about, so a run that waits for you opens where you approve it. |
| **Mark all read** | Every notice is marked read. |
| **Show more** | Earlier notices are listed. |
| **Email settings** | The email switches below open. |

With no notices yet, the panel reads “Nothing yet. A notice arrives when a
Worker’s run finishes, fails or waits for your approval.”

<!-- media: notices-panel | The Notices panel opening a run that waits for approval | Worker with a send step runs → bell shows 1 → open Notices → choose the notice → the run opens on its approval -->

## Which notices are emailed

An emailed notice has the notice’s words and one button: **Open the Worker**,
or **Review and approve** for a run that waits for you. The switches are in
**Settings → Email notices** in the web app and **Settings → General** in the
desktop app. A switch takes effect as soon as it is changed.

| Switch | What it covers | Default |
|---|---|---|
| **A run fails** | “A Worker’s run stopped with an error.” | On |
| **A Worker waits for your approval** | “A run stopped before sending or changing something.” | On |
| **A watched address goes down** | “An uptime Worker saw an outage.” | On |
| **A watched address is back** | “An uptime Worker saw it recover.” | On |
| **A run finishes** | “Every finished run. This can be a lot of mail.” | Off |

!!! tip
    Keep **A Worker waits for your approval** on: an approval nobody answers
    expires after 7 days and the step isn’t done. See
    [How Workers work](../workers/how-workers-work.md#you-dont-answer-an-approval).

## Emails from Ysra

Every email Ysra sends looks the same: light, short, one headline, a line or
two, one button, and links to ysra.ai, the docs and help at the foot. None
carries technical error text.

| Email | Its button |
|---|---|
| An invitation to an organisation (“… invited you to join Acme on Ysra”) | **Join your team** |
| Code work ended: **Ready**, **Needs you** or **Didn’t finish**, with the thread’s title and one sentence | **Open in Ysra** |
| A visitor left a question for a person, quoting it | **Open the conversation** |
| A Worker notice | **Open the Worker** or **Review and approve** |
| Account emails: verifying your address, a new password, billing | The step to take, such as **Verify email** or **Choose a new password** |

## Related

- [How Workers work](../workers/how-workers-work.md) — run states and approvals behind each notice.
- [Runs and approvals](../workers/runs.md) — where a notice opens.
- [Settings](settings.md) — the web app’s email switches.
- [Ysra Desktop settings](../desktop/settings.md#general) — the same switches in the desktop app.