> ## Documentation Index
> Fetch the complete documentation index at: https://resources.athenaintel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Know when it finishes

> Set run notifications, read statuses, and review or retry a failed AOP run

Set your Monday assistant to tell you when a triggered run finishes or fails. You will configure notifications for your Agent Operating Procedure (AOP), then read its run list and inspect a failure. This helps you follow the work without keeping the run open.

**Before you start:** Watch [Smarter run forms](03-smarter-run-forms.mdx). Open your AOP's configuration and use its existing runs to follow the status examples.

<Frame caption="AOPs in depth · Episode 4 · Know when it finishes · 3:23">
  <video controls muted={false} playsInline preload="metadata" className="w-full aspect-video" poster="/images/courses/aops-in-depth/ep4-poster.jpg" src="https://mintcdn.com/athenaintelligence-e46bc9d3/PqPuebc_5Izuo949/images/courses/aops-in-depth/ep4.mp4?fit=max&auto=format&n=PqPuebc_5Izuo949&q=85&s=16981c3fb9c09fe7dc1e05f0ae52c233" data-path="images/courses/aops-in-depth/ep4.mp4" />
</Frame>

<Accordion title="Steps in this video">
  1. Turn on notifications
  2. Email the right people
  3. Post to a webhook
  4. Read the run statuses
  5. Retry a failed run
  6. Analyze a run
  7. Know when it finishes
</Accordion>

## Set notifications and follow a run

1. Open **Configuration** and scroll to **Notifications & Chaining**. Turn on **Notify on failure**, **Notify on success**, or both. **Notification Channels** appears when either switch is on.
2. Choose **Email** to send notifications to your account email address. If you also want to notify the person who started the work, select **Email the person who triggered the run**. For SharePoint uploads, this is the file's **Modified By** user. For email triggers, it is the sender.
3. To send run status to an external endpoint, choose **Webhook** and enter **Webhook URL**. Use an HTTPS address. An empty field shows **Enter a webhook URL.** An HTTP address shows **Webhook URLs must use HTTPS.**
4. Open **Runs**. Read **Status** for each row. The video shows **Running**, **Completed**, **Failed**, and **Waiting for Approval**. Use the **Status** filter to select **Running**, **Completed**, or **Failed**.
5. On a failed row, click the arrow beside **Failed**. Read the message and error text. After reviewing the cause, click **Retry This Run** to start it again. Look for **AOP retry started**.
6. Open a row's menu and choose **Analyze This Run**. This asks Athena to review that run and recommend improvements. Failed rows also offer **Retry This Run** in their menu.

## Good to know

* Both notification switches start off. Each person sets their own notification preferences; settings are stored per user.
* Notifications in this card cover triggered executions. The **Webhook** endpoint receives success and failure events and must use HTTPS.
* **Waiting for Approval** means a person needs to approve. It is a row status, but it is not an option in the **Status** filter shown here.
* The red badge on **Runs** counts failed runs. Expand a failed row to read its error before retrying.
* **Retry This Run** starts a new run and opens it in chat. It does not resume the failed run.

## Previous and next

[Previous: Smarter run forms](03-smarter-run-forms.mdx) · [Next: Chain AOPs and monitor them](05-chain-aops-and-monitor-them.mdx)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.