# Automations on Ontology scenarios

[Automate](../overview/index.md) can run automations on [Ontology scenarios](../../ontology/overview-ontology-scenario/index.md). When you enable an automation to run on scenarios, the automation listens for active scenarios represented by objects belonging to the configured scenario object types. The automation continues to run on the main Ontology and also runs on any detected scenarios.

## Use automations on Ontology scenarios

To configure an automation to run on Ontology scenarios, you must first have a scenario object type. For setup instructions, see [Store scenario metadata as objects](../../ontology/persisted-scenario/index.md).

To extend an automation to Ontology scenarios:

1. Open the automation edit page and select **Settings**.
2. Under **Scenario configuration**, choose to **Enable automation to run on scenarios**.
3. Under **Scenario object types**, add the scenario object types that represent the scenarios on which you want the automation to run.
4. Complete the remaining configuration and save the automation.

![The Scenario configuration settings with Enable automation to run on scenarios enabled and a scenario object type selected.](../../../assets/2287d619346a57b41b9de0be77fe91cee34ba0db04846ad9994f8bb1adb04580.webp)

## Expected behavior

When you enable an automation to run on scenarios, the following behavior applies:

* The automation evaluates its conditions and executes its effects on both the main Ontology and every scenario represented by an object belonging to the configured scenario object types.
* The automation evaluates conditions independently on the main Ontology and on each scenario.
* When a scenario is deleted, Automate stops monitoring it and no longer evaluates conditions or executes effects on it. This includes scenarios that are [automatically deleted when their lifespan ends](../../ontology/overview-ontology-scenario/index.md#time-to-live).

### Effect execution on scenarios

When a condition is met on a scenario, effects behave as follows:

* Actions execute against the scenario.
* Logic and function effects execute in the context of the scenario.

Notification effects also use the context of the scenario on which the automation is executing:

* [Dynamic recipients](../effect-notification/index.md#dynamic-recipient-definition-via-object-properties) are determined from object property values in the scenario.
* Functions that produce [function-generated notification content](../effect-notification/index.md#function-generated-notification) execute in the scenario context. The generated content therefore reflects object and property values from the scenario.

## Supported conditions and effects

Not all Automate [conditions](../condition-objects/index.md) are currently supported on Ontology scenarios.

The following conditions are **supported** on Ontology scenarios:

* [**Time**](../condition-time/index.md): Triggers when a specific time is reached; for example, "Every Monday at 9 AM."
* [**Objects added to set**](../condition-objects/index.md#objects-added-to-set): Triggers when a new object appears in a predefined object set.
* [**Objects removed from set**](../condition-objects/index.md#objects-removed-from-set): Triggers when an object leaves a predefined object set.
* [**Objects modified in a set**](../condition-objects/index.md#objects-modified-in-set): Triggers when an object is modified in a predefined object set.
* [**Run on all objects**](../condition-objects/index.md#run-on-all-objects): Periodically runs effects on all objects in a given set.

The following conditions are **not currently supported** on Ontology scenarios:

* **Threshold crossed:** Triggers and remains in the triggering state when a metric threshold is crossed.
* **Automation dependency:** Triggers after another automation completes. See [Known limitations](#known-limitations).
* **Time series:** Triggers when a time series threshold is crossed.
* **Stream \[Beta]:** Triggers on any new records in a [stream](../streaming/index.md).
* **Metric changed \[Sunset]:** Triggers when an aggregated object set metric increases or decreases.

All Automate [effects](../effects/index.md) are supported on Ontology scenarios:

* [**Action:**](../effect-actions/index.md) Executes an action when the condition is met.
* [**Logic:**](../effect-logic/index.md) Executes an AIP Logic function when the condition is met, then either stages or applies the generated actions.
* [**Function \[Beta\]:**](../effect-function/index.md) Executes a function when the condition is met. These functions cannot perform Ontology edits.
* [**Notification:**](../effect-notification/index.md) Sends a notification to selected recipients, with optional Notepad attachments.

## Permissions

Automations use the [automation owner's permissions](../permissions/index.md#permissions-for-executions) to evaluate conditions and execute effects. For an automation to run on an Ontology scenario, the owner must have access to both the configured scenario object type and the scenario. The automation cannot run on scenarios that the owner cannot access.

## Known limitations

* Automations can only run on scenarios represented by scenario object types configured in the automation settings.
* An automation can track up to 100 scenarios. You cannot save an automation that targets more than 100 scenarios. If the target grows beyond this limit after you save, scheduled evaluations will fail before Automate evaluates conditions or executes effects.
* Automations cannot run on [temporary scenarios](../../ontology/temporary-scenario/index.md).
* Not all conditions are supported on Ontology scenarios. See [Supported conditions and effects](#supported-conditions-and-effects) for the full list.