# Explore workflow outputs

The workflow detail page focuses on the records produced by execution. Use it to confirm the result, inspect intermediate persisted data, and follow a record into its canonical Data detail.

## Choose the scope

Start with the run selector. The latest-run scope follows the most recent execution; selecting a particular run keeps the investigation focused. **All runs** shows accumulated records across executions rather than just the latest one.

Then choose one or more jobs using the pipeline or Job filter. Use All to select every job and Clear to deselect them; an empty job selection shows no rows. Add a Type filter and Search outputs text when you need a narrower view.

1. Select the run you want to inspect.
2. Select the producing job.
3. Narrow by record type or search text.
4. Expand a row to read its payload.
5. Use **Open** to inspect the record in Data.
6. Clear filters before concluding that records are absent.

## Read counts accurately

The total describes the server's record scope; the rows loaded into the table can be only part of that total. Some search and multi-job/type filtering applies to loaded records, so a filtered count is not always an exhaustive search of every unloaded page. Load more data or use an appropriate Data view for a broader investigation.

A streaming indicator means records can continue arriving. Wait for the relevant run to finish before comparing final totals.

## Understand what appears

Durable records form the persistent explorer. When a successful run has no derived records, the page can show retained job previews instead, preferring connector-write destination previews where available. A preview can be a limited sample rather than the complete external dataset, and it is not necessarily a canonical Data record. A step's execution preview and its durable dataset serve different purposes. Intermediate data may be kept for recovery without being published as an app data source.

The payload can include the extracted or transformed fields, source references, record type, and execution provenance. Preserve these links when investigating where a value came from.

External destinations can receive writes without creating the same rows in this explorer. Check that destination separately. Likewise, a proposal awaiting human review is not an approved business fact merely because its workflow succeeded.

See [data sources](/docs/workflows/data-sources), [Data](/docs/data/overview), and [monitoring runs](/docs/workflows/monitor-runs).