# Logs

Workflow logs help you inspect what happened after a run starts, whether that run came from the dashboard or from a live workflow deployment. Use this page to review recent workflow activity, filter the runs you care about, and open a run detail sheet with trace data and output.

## Overview

The workflows logs UI is a table-driven view under **Logs** in the workflows section. It supports source filtering from the sidebar, date range filtering from the header, and row-level inspection through a detailed run sheet.

When you open a completed run, the detail sheet combines summary data, a trace waterfall, request details, output, start inputs, and async webhook information when present.

## How do I open workflow logs? <a href="#open-workflow-logs" id="open-workflow-logs"></a>

Open **Workflows** in the sidebar.

Click **Logs** in the workflows section menu.

Use the **Source** group in the sidebar when you want to switch between **All Sources**, **Dashboard**, and **Live**.

Use **Dashboard** when you only want runs started from the editor or dashboard UI. Use **Live** when you only want runs associated with a workflow deployment variant.

## What can I filter in workflow logs? <a href="#filter-workflow-logs" id="filter-workflow-logs"></a>

Use the date range control in the header to choose a custom range or a preset such as the last one, seven, 30, or 90 days.

Use **API keys** to narrow the table to runs started with one or more workspace API keys.

Use **Workflow** when you want to isolate runs for a single workflow.

Use **Trigger** to switch between **All**, **Async**, and **Sync** runs.

Click **Clear filters** to reset the active filter state.

## What's tracked in the workflow logs table?

The main logs table shows summary fields for each run, including:

* **Completed At**
* **Name**
* **Tools**
* **Status**
* **Total Cost**
* **Duration**
* **API Key**
* **Collaborator**

For live runs, the **Name** column can also show the deployment variant badge, including the variant name and version number.

The **Tools** column reflects the providers or step sources that contributed completions to the run.

## How do I inspect a workflow run? <a href="#inspect-workflow-run" id="inspect-workflow-run"></a>

Click a completed row in the logs table.

Fetch Hive opens a run detail sheet on the right.

The header shows the run ID, status, start time, deployment variant badge when present, and an **Async** badge when the run uses async delivery.

The summary strip below shows the workflow, duration, cost, tools, and owner for that run.

If the workflow still exists and is not archived, the workflow name in the summary strip links back to the workflow editor.

## Traces <a href="#traces" id="traces"></a>

Use the trace waterfall on the left side of the run detail sheet to understand how the run progressed over time.

Each span helps you inspect a specific part of the run, such as the incoming request, workflow start, tool activity, LLM activity, and workflow completion.

When you select a span, the right side updates to show the span details and any linked completion data. Depending on the selected span, this can include:

* model response data
* request details
* start inputs
* output content
* metadata
* token and cost breakdowns

This is the main debugging view for workflow runs. Start here when you need to understand which part of the workflow was slow, failed, or produced the wrong result.

## How do I inspect output, async configuration, and webhook logs? <a href="#inspect-output-and-webhooks" id="inspect-output-and-webhooks"></a>

Open a run from the logs table.

Select the request or completion spans in the trace panel to switch the right-side details.

Use the output section when you want to inspect the final workflow result from the **workflow\.complete** span.

If the run is async, the request-level details can also show **Async Configuration** with the callback URL used for that run.

If webhook delivery logs are present, the same sheet can show **Webhook Logs** with callback URL, retry count, response code, payload, response body, and a **Retry** action for failed webhook attempts.

## Notes

* The logs table updates in response to workflow run status changes, so recent runs can refresh while you are viewing the page.
* Running rows are not the main entry point for deep inspection. Open a completed run when you want the full detail sheet and trace view.
* Async webhook details are only visible when the selected run actually used async delivery.

See also: [Publishing and Versioning](https://docs.fetchhive.com/workflows/publishing-and-versioning), [Async and Webhooks](https://docs.fetchhive.com/workflows/async-and-webhooks), and [Run with API](https://docs.fetchhive.com/workflows/run-with-api)