Automation Tasks
This page provides detailed information about automation tasks in AZExecute, including task types, configuration options, and lifecycle management.
Task Properties
Every automation task has the following core properties:
Name:
A unique, descriptive name for the task. This name is used throughout the interface to identify the task.
Description:
Optional detailed description of the task's purpose and functionality. This helps other operators understand what the task does.
Type:
Either "General" for standalone tasks or "Certificate" for tasks linked to ACME certificate templates. Certificate tasks have additional step types available specifically for certificate management.
Created On:
Timestamp when the task was first created.
Last Modified On:
Timestamp of the most recent modification to the task configuration.

Task Types
General Tasks
General tasks are the most common type and can be used for any automation scenario. They support all available step types and are not linked to any specific Azure resource or template.
Certificate Tasks
Certificate tasks are automatically linked to ACME certificate templates and are designed specifically for certificate deployment and renewal workflows. When a certificate is renewed, the associated automation task can be triggered automatically.
Certificate tasks have access to additional step types:
• Certificate Install - Deploy the renewed certificate to target machines
• Azure Key Vault - Update certificates in Azure Key Vault

Managing Task Steps
Steps are the building blocks of automation tasks. Each step performs a specific action, and steps execute in sequence according to their execution order.
Adding Steps
Click the "Add Step" button on the Steps tab to open the step creation dialog. Select a step type and configure its settings, then click "Add Step" to save it to your task.
Reordering Steps
Use the up and down arrow buttons on each step to change its position in the execution order. After reordering, click "Save Step Order" to persist the changes.
Editing Steps
Expand any step to view and modify its configuration. Each step type has different configuration options. After making changes, click "Save Step" to persist them.
A "Unsaved changes" indicator appears next to steps that have been modified but not saved.
Enabling/Disabling Steps
You can temporarily disable a step without deleting it. Disabled steps are skipped during task execution. Click the "Disable" or "Enable" button on any step to toggle its state.
Removing Steps
Click the "Remove" button on any step to delete it from the task. This action cannot be undone. The execution order of remaining steps will automatically adjust.
Step Execution Settings
Each step has advanced execution settings that control how it behaves within the task workflow:
Execute in Parallel:
When enabled, this step will run concurrently with previous steps instead of waiting for them to complete. This is useful for independent operations that can run simultaneously to reduce overall execution time.
Stop on Failure:
Enabled by default. When a step fails, the entire task execution halts and no further steps run. Disable this option to continue executing remaining steps even if this step fails.
Delay Before Next Step:
Specify a wait time in minutes before the next step begins execution. This is useful when you need to wait for external systems to process changes before proceeding.

Task Configuration Tabs
The task configuration page has three main tabs:
Task (Info Tab):
Configure basic task properties such as name, description, and type. This tab also displays warnings if the task has unlinked custom parameters.
Steps:
Add, configure, and manage the steps that make up your automation workflow. This is where you build the actual logic of your task.
History:
View all past executions of this task, including status, duration, and detailed step results. Use this tab to troubleshoot failures and monitor task performance.

Parameter Validation Alerts
If your task uses script or runbook steps with custom parameters, AZExecute will automatically detect if there are existing parameters that could be linked to the task.
An alert banner appears at the top of the configuration page showing:
• The number of unlinked parameters detected
• A quick link to review and link parameters
Linking parameters allows you to prompt users for input when executing the task, making it reusable across different scenarios. Learn more in the Custom Parameters documentation.
Deleting Tasks
To delete an automation task, navigate to the Automation Tasks list, find the task you want to delete, and click the "Delete" button in the options column.

If you encounter any issues or need further assistance, please contact us at
info@azexecute.com. Our support team is here to help you.