> ## 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.

# Chain AOPs and monitor them

> Connect AOPs, map their inputs, and filter, stop, export, or analyze their runs

Let your Monday assistant start the next task when its run succeeds or fails. You will connect Agent Operating Procedures (AOPs), map the next AOP's inputs, and manage runs from the run list. This gives each part of your workflow its own instructions and lets you follow the handoff.

**Before you start:** Watch [Know when it finishes](04-know-when-it-finishes.mdx). Revisit [Smarter run forms](03-smarter-run-forms.mdx) for structured output. Have a follow-up AOP ready to select.

<Frame caption="AOPs in depth · Episode 5 · Chain AOPs and monitor them · 3:41">
  <video controls muted={false} playsInline preload="metadata" className="w-full aspect-video" poster="/images/courses/aops-in-depth/ep5-poster.jpg" src="https://mintcdn.com/athenaintelligence-e46bc9d3/PqPuebc_5Izuo949/images/courses/aops-in-depth/ep5.mp4?fit=max&auto=format&n=PqPuebc_5Izuo949&q=85&s=a9f3ba0f100ba33b69fe29cea5feb2c8" data-path="images/courses/aops-in-depth/ep5.mp4" />
</Frame>

<Accordion title="Steps in this video">
  1. Open AOP Chaining
  2. Chain on success
  3. Map each input
  4. Chain on failure
  5. Know the chain rules
  6. Find every run
  7. Filter by status
  8. Stop several runs
  9. Export and analyze
  10. Chain and monitor at a glance
</Accordion>

## Connect the next AOP

1. Open **Configuration**. Under **Notifications & Chaining**, find **AOP Chaining**. You can choose **Chain on success** and **Chain on failure** separately.
2. Under **Chain on success**, use **Search for an AOP to chain...**. Select the AOP that should run next. Its title appears with **Remove**, and its inputs load below.
3. Under **Pre-fill inputs for chained AOP:**, choose a source for each input. Choose **Static value** to enter a fixed value. To use a field from the parent's structured output, choose **Parent:** followed by the field name. You see **Filled from parent output at run time**.
4. Under **Chain on failure**, select the AOP that should handle a failed run. Enter fixed values for its inputs. A failed parent may not produce structured output.

## Monitor and manage runs

1. Open **Runs**. **My runs** lists runs you started. **All runs** includes everyone's runs and adds **Created By**. Open the chained AOP's **Runs** tab to find runs with **Chain** under **Trigger**.
2. Use **Status** to select **Running**, **Completed**, or **Failed**. You can select more than one. Expand a failed row to read its error and find **Retry This Run**.
3. To stop several running runs, select their checkboxes. With two selected, click **Stop 2 Selected**. Review **Stop AOP Runs**, then click **Stop** to confirm. The resulting row status is **Cancelled**.
4. Use **Export as CSV** to download the runs you see. In the **Runs** tab menu, choose **Analyze & Improve Prompt** to ask Athena to review recent runs and suggest prompt changes.

## Good to know

* Cycles are blocked. An AOP cannot chain back into its own chain. The current AOP is excluded from its own picker.
* A chain runs up to three hops: the original AOP plus up to three follow-up AOPs.
* Success chains can use fixed values or fields from the parent's structured output. Failure chains use fixed values only.
* Notifications and chaining are scoped per user. Configure the handoffs for your own runs.
* Only running rows have stop checkboxes. You confirm before stopping selected runs. **Export as CSV** is disabled when there are no rows.

## Previous and next

[Previous: Know when it finishes](04-know-when-it-finishes.mdx) · [Next: AOP reference](../../pillars/applications/aops.mdx)

[Back to the course overview](index.mdx)


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