---
id: troubleshooting.missing-outputs
title: Missing Outputs
summary: Separate a missing managed Run response from an unmatched row in an imported output-only Run.
kind: error
product_area: troubleshooting
status: stable
updated: 2026-08-23
canonical: /docs/troubleshooting/missing-outputs
---

# Missing Outputs

Use this when an Evaluation Run has no response for an intended Case. First identify whether the evidence came from managed Harness execution or an imported output-only Run.

## Symptom

A managed Run is incomplete or has a failed or unevaluable Case attempt, or an imported output-only Run shows an unmatched Case row. An input-only Case by itself is not an error: managed execution is expected to generate its response.

## Likely causes

- Managed execution failed, stopped, or could not evaluate the Case.
- The wrong saved Harness Version or execution settings were selected.
- An external output row has a missing, unknown, or duplicate immutable Case ID.
- The imported file omitted Cases that the output-only Run was intended to cover.

## Diagnostic checks

- Open the Run and check its lifecycle, attempts, failed Cases, and selected Harness Version.
- Confirm that the Case belongs to the immutable Benchmark Version used by the Run.
- For imported outputs, compare external identifiers with the immutable Case IDs shown by the mapping surface.
- Confirm that the intended output column and candidate metadata were selected before import.

## Fix

- For managed execution, correct the Harness or execution problem and start a new Run against the same Benchmark Version when that boundary is still intended.
- For imported outputs, correct the external rows and repeat mapping with immutable Case IDs.
- Keep managed and imported-output diagnoses separate; an imported response does not become a saved Harness Version.
- Change the current Dataset and create a new Snapshot only when Case membership itself is wrong—not merely because a Run response is missing.

## Prevention

- Save the exact Harness Version before managed execution and review execution settings.
- Export or preserve immutable Case IDs through external generation.
- Validate several mapped rows before creating an output-only Run.
- Use Run Metadata to identify the candidate or external output set without pretending it is a Harness Version.

## Related task pages

{% related-card-grid title="Related task pages" %}
- [Import and prepare cases](/docs/operating-manual/import-and-prepare-cases)
- [Run a benchmark](/docs/benchmark-evaluations/run-evaluation)
- [Map external outputs](/docs/benchmark-evaluations/output-mapping)
{% /related-card-grid %}

## Related reference pages

{% related-card-grid title="Related reference pages" %}
- [Target model outputs](/docs/object-model/outputs)
- [Input-only and output-attached cases](/docs/assets/cases)
- [Benchmarks](/docs/object-model/benchmarks)
{% /related-card-grid %}

## Source confidence

Code-backed: the Run modal and Run detail establish managed execution identity and status; the output-mapping modal and List surface establish imported output-only Runs and unmatched Case handling. Input-only Cases are valid inputs to managed execution.