---
title: Monitor workflow execution
description: Track workflow runs in real time, review execution history, and troubleshoot workflow failures in Kibana.
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/8145/explore-analyze/workflows/authoring-techniques/monitor-workflows
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud Hosted
  - Elastic Cloud Serverless
  - Elastic Cloud on Kubernetes
  - Elastic Stack
  - Kibana
applies_to:
  - Elastic Cloud Serverless: Generally available
  - Elastic Stack: Generally available since 9.4, Preview in 9.3
---

# Monitor workflow execution
After you run a workflow, you can track its progress in real time, review past executions, and diagnose any failures. This page explains how to use the execution panel and logs on the **Executions tab** to understand what happened during a workflow run.
<admonition title="Requirements">
  To use workflows, you must turn on the feature and ensure your role has the appropriate privileges. Refer to [Set up Workflows](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/8145/explore-analyze/workflows/get-started/setup) for more information.You must also have the appropriate subscription. Refer to the subscription page for [Elastic Cloud](https://www.elastic.co/subscriptions/cloud) and [Elastic Stack/self-managed](https://www.elastic.co/subscriptions) for the breakdown of available features and their associated subscription tiers.
</admonition>


## Execution-based billing

<applies-to>
  - Elastic Stack: Generally available since 9.5
  - Elastic Cloud Hosted: Generally available
</applies-to>

On Elastic Cloud Hosted, [Workflows](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/8145/explore-analyze/workflows) is billed based on workflow executions. Each workflow run counts as one execution, including runs that fail, are canceled, or time out. Runs skipped by concurrency controls are not metered.
The first 10,000 workflow executions each month are included. Additional executions are billed at the published tiered rates.
When a workflow invokes an agent, the Elastic Agent Builder execution is metered separately. Refer to the [Hosted add-ons pricing table](https://cloud.elastic.co/cloud-pricing-table?productType=stack_hosted&group=addons&dimension=executions) for current rates and tier breakpoints.
This billing model doesn't apply to Elastic Cloud Hosted [FedRAMP authorized Cloud offerings](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/8145/deploy-manage/deploy/elastic-cloud/fedramp), which remain under promotional pricing.

## Monitor execution

When a workflow runs, the execution panel displays:
- **Real-time logs**: Each step appears as it executes.
- **Status indicators**: Green indicates success and red represents failure.
- **Timestamps**: The duration of each step.
- **Expandable details**: Click any step to examine details such as input parameters, output data, and execution timelines.


## See what triggered a run

<applies-to>
  - Elastic Cloud Serverless: Generally available
  - Elastic Stack: Generally available since 9.5
</applies-to>

Every execution begins with a trigger entry that shows how the run started, such as a manual run, a schedule, an alert, or an event. Expand this entry to see the input the workflow received, including the full event payload for [event-driven](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/8145/explore-analyze/workflows/triggers/event-driven-triggers) runs. This lets you trace an execution back to the event or action that started it, which is especially useful when workflows react to one another through event-driven triggers.

## View execution history

To review past runs, select the **Executions** tab, then click each run to see detailed logs. Workflow runs can be `Pending`, `In progress`, `Completed`, or `Failed`.

## Troubleshoot errors

When a workflow fails, open the failed execution from the **Executions** tab, then find the step with the error indicator. Expand the step to view the error message and to learn more about the root cause, such the input that caused the failure. After fixing an error, save the workflow before running it again.
Common issues that can cause failures:

| Issue            | Cause               | Solution                              |
|------------------|---------------------|---------------------------------------|
| Syntax error     | Invalid YAML        | Check indentation and formatting.     |
| Step failed      | Action error        | Review step configuration and inputs. |
| Missing variable | Undefined reference | Verify variable names and data flow.  |