# Find missing or unexpected results

An empty view can mean no matching results, the wrong selected run, a filtered-out record type, an unready source, or an invalid binding. Work through those possibilities before rerunning the entire process.

## Check the process

Open the workflow and select the intended run. Check each step's status and input/output counts. A completed workflow can contain records describing per-item errors. A source step returning zero records can be a legitimate empty result.

Check connection access, selected file or prefix, date window, and search terms. A folder or storage search can have an empty page with a continuation when the scan is incomplete; continue before concluding nothing matches.

## Check the view

Clear app, table, date, and record-type filters. Confirm the selected document or table. Verify that the component reads the correct data source and that source reads the intended workflow or app output.

A paginated view is not necessarily the whole collection. A displayed total, page size, and an edition identifier have different meanings. Do not treat a sequence key as a count of visible rows.

## Check completeness

Extraction can return fields while still reporting missing evidence, unresolved rows, or coverage limits. Topic News can retain snippets when enrichment is unavailable. A review projection includes approved changes for its date and excludes pending proposals.

## Fix the narrow cause

Correct the binding or filter when the records exist. Repair source access before rerunning a failed read. Use a full run only when you intend full reprocessing; incremental mode can reuse a valid baseline. After a correction, inspect the resulting records and their provenance.