The Execution and transaction Tracking tabs provide visibility into automation performance and the resulting business impact. Depending on your selection, these tabs track either automation executions or the transactions processed within those executions, including associated failure costs and missed benefits.

This enables you to monitor reliability, quantify impact, and identify where automation failures might affect business value.

Execution tracking

Execution tracking offers visibility into automation performance at the run level, focusing on execution outcomes and the impact of failures. When execution tracking is selected, failure-related costs are tracked directly at the automation level instead of the opportunity level. This allows teams to clearly identify which specific automations are contributing to failure costs and operational risk. Execution metrics typically summarize how often an automation runs, the number of successful and failed executions, and the financial impact of those failures over selected time periods, such as today, the last 7 days, or recent months.

Transaction tracking

Transaction Tracking, shifts the focus from automation executions to the individual business transactions processed by an automation. Since each run might handle multiple transactions, tracking at this level provides a more precise measure of operational efficiency and business impact. Metrics such as successful transactions, failed transactions, failure costs, and missed benefits offer insight into how effectively an automation is delivering value. This approach is especially valuable for high-volume automations, where a single execution failure can affect numerous transactions and significantly impact business outcomes.

Deployment details

Cost per execution failure: Represents the monetary cost assigned to each failed automation execution. This value is used to calculate the total failure cost displayed in tracking metrics and reports. The cost is applied and tracked at the automation level rather than at the opportunity level.

Deployment notes: An optional text field used to capture release-specific information such as configuration changes, assumptions, or operational notes related to the deployment. This helps provide context when reviewing performance or failures later.

Automations

Automations provides the following details:

  • Name: Name of the automation selected for tracking. This is a clickable link that allows users to navigate to automation-specific details.
  • Automation ID: Unique identifier for the automation. This ensures accurate tracking and reporting, especially when automations have similar names across environments.
  • Control Room: Indicates the Control Room instance where the automation is deployed and executed. This helps users distinguish between different environments such as production, test, or multiple Control Room integrations.
  • Failure cost: Displays the cost incurred due to failed executions or failed transactions for the automation, based on the configured cost per execution failure and observed failures during the selected time period.
  • Missed benefit: Represents the estimated business value lost due to automation failures. This is typically derived from unsuccessful transactions or incomplete processing and helps quantify the opportunity cost of failures.

Execution or transaction metrics

Provides a summarized view of automation performance at the execution or transaction level. Metrics are aggregated by time ranges such as today, last 7 days, this month, last 3 months. These metrics help teams monitor execution reliability, identify trends, and detect sudden increases in failures.