AOPs in depth · Episode 5 · Chain AOPs and monitor them · 3:41
Steps in this video
Steps in this video
- Open AOP Chaining
- Chain on success
- Map each input
- Chain on failure
- Know the chain rules
- Find every run
- Filter by status
- Stop several runs
- Export and analyze
- Chain and monitor at a glance
Connect the next AOP
- Open Configuration. Under Notifications & Chaining, find AOP Chaining. You can choose Chain on success and Chain on failure separately.
- 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.
- 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.
- 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
- 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.
- 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.
- 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.
- 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.

