# Run history

To see the run history for a Function, Action or automation, navigate to the resource, then select the **Run history** tab. This provides a complete view of all executions over the past 30 days.

![The Run history tab displays a table of recent executions.](../../../assets/47b9c15f7ee431e69495ff803eb207f33c96e5668a0ba2133bad2b7f68298e90.webp)

## Run history data

The **Run history** table includes:

* **Timestamp:** When each execution finished.
* **Status:** Success (✓) or failure (✗).
* **Runtime:** Total execution time.
* **Caller:** The resource that triggered the execution; this can be a Workshop application, Agent, Third-party application, Automation, Action, or other system component.
* **Source executor:** The top level executable resource type (limited to Function, Action, or Automation) in the call chain.

The run history displays executions from the past 30 days, sorted by timestamp.

## Limitations

* **UDFs in Pipeline Builder:** Execution history is not available for user-defined functions (UDFs) run from a sidecar container, such as in [Python](../../functions/python-functions-builder/index.md) or [Java](../../transforms-java/user-defined-functions/index.md) UDFs.

## Filter run history

You can filter the results by:

* **Status:** View successful or failed executions.
* **Timestamp range:** View executions within a specified date range.
* **User:** View executions triggered by a specific user.
* **Run time range:** View executions within a specified duration range.
* **Version:** View executions for a specified version (only applicable for functions).
* **Caller:** View executions originating from a specified resource.
* **Failure type:** View executions that failed for a specific reason. Learn more about [function](../../functions/function-metrics/index.md#function-failure-types) and [action](../../action-types/action-metrics/index.md#action-failure-types) failure types.

If more than one filter is specified, the results will be filtered to include only those that match all specified filters.

## Inspect a specific execution

To inspect a specific execution, select the **View log details** option to access the full trace and debugging information.

![View log details for a specific execution in the Run history table.](../../../assets/4439f93a16be9181f25612600917403f20c6e207f14fb22dd8cdc9dbd731985f.webp)

## Next steps

* View [trace details](../trace-view/index.md) to understand execution flow.
* Access [service logs](../service-logs-and-debugging/index.md) for detailed debugging.
* Configure [log permissions](../log-permissioning/index.md) to enable log visibility.