Actions#
The Action is the operation that the Automation Scheduled Action (ASA) performs on an entity once it is confirmed ready.
Each Scheduled Action has exactly one configured Action. The Action only runs after all configured prerequisite steps ( Pre-Conditions, Detector, and Acceptance Gates) have cleared successfully.
How It Works#
- All previous steps pass: Pre-Conditions, Detector, and Acceptance Gates.
- The configured Action for the ASA task runs.
- One of the following outcomes occurs:
- Ignored - the action would result in no change (for example, the entity is already on the target version). No changes are made.
- Failed - the action could not complete. The task is marked as failed.
- Succeeded - the action completed. The flow moves on to Post-Action Validation.
Actions are the only step in the flow that change system state. All other steps are read-only checks.
Action Options#
The Action section allows you to select one of 3 possible actions:
Stops the current Automation Controller Instance and updates it with a new one using the specified revision and version of the same controller.
Specify the Automation Controller you want to update, as well as the target revision and version.
If the running instance is already on the specified revision and version, the action does not run and the task is marked as Ignored.
Ideal for:
- Rolling out a new controller version to instances without manual intervention.
- Scheduling version updates to happen only when the entity is idle.
Result:
- The instance is stopped, and updated with a new one with the specified revision and version.
- If the target is already running, the task is marked
Ignoredwith no changes made.
Stops the current Automation Controller Instance and updates it with a new one hosted by the specified Automation Manager.
You must specify the target Automation Manager for the change.
If the instance is already hosted by the specified manager, the action does not run and the task is marked as Ignored.
Ideal for:
- Moving instances between managers as part of infrastructure changes.
- Rebalancing workloads across managers during a maintenance window.
Result:
- The instance is stopped, and updated with a new one under the specified manager.
- If the target manager is already hosting the instance, the task is marked
Ignoredwith no changes made.
Runs a DEE action as the scheduled action. The DEE action defines the full behavior.
Ideal for:
- Custom maintenance operations not covered by the built-in action types.
- Actions that depend on external systems or complex business logic.
You must specify the DEE action to use. Make sure its inputs and outputs match the DEE contract:
| Direction | Key Name | Data Type | Description |
|---|---|---|---|
| Input | Task | AutomationScheduledActionTask | Context about the task being executed. |
| Output | Result | Boolean | true = Pass, false = Fail. |
Table 1: Action DEE Contract
Result:
- Runs the configured DEE action and uses the boolean output to determine success or failure.
Actions stop and restart the instance
Both Update Controller Version and Change Automation Manager stop and update the running instance, creating a new one. Make sure the Detector and Acceptance Gates are set up to confirm the entity is idle before the action runs. Acting on an instance that is still processing work will interrupt it.
Configuration Steps#
In the Create Scheduled Action wizard:
- Locate the Action section, after the Detector section.
- Select one of the available action types.
- Fill in the required fields for the selected action.
- Proceed to the next section.
Only one action can be configured per Scheduled Action.
