Execution & History

This page explains how automation task executions are started, how run progress is shown, and how to investigate run results.


Where Executions Start

Task configuration: use the Execute action for the selected automation task

Published Tasks: authorized users can execute published tasks from the user-facing list

If a task has linked parameters, the execute dialog requests values before queuing the run.

Execute Task Dialog

Execution History View

In task history, each run appears as an expandable entry with key metadata and step-level results.

• Run timestamp, current status, and completed-step count

• Task-level variables captured during execution

• Step table with started/ended timestamps and per-step status

• Expandable step details for parameters, output, and error details

• Pagination for historical runs

Execution History Overview

Live Monitoring and Control

While a run is still active, the history UI refreshes status and step data automatically.

• Active runs are refreshed periodically until they reach a final state

• The Cancel action is available for runs that are not yet in a final state

Live Run Monitoring

Common Status Values

Created: run is queued/initialized

Running: one or more steps are still executing

Completed: run finished successfully

Failed: one or more steps failed

Cancelled: run was cancelled


Troubleshooting Workflow

1. Open the failed run from history

2. Identify the failed step in the step table

3. Expand the step and review error details and output

4. Verify parameter values and task variables for that run

5. Fix the task/step and execute again



If you encounter any issues or need further assistance, please contact us at

info@azexecute.com

. Our support team is here to help you.

An unhandled error has occurred. Reload 🗙
An unhandled error has occurred. Reload 🗙