# Case imports and input mapping
Generated: 2026-11-13T08:01:29.042Z
Source build: local
Canonical docs: https://teammately.ai/docs
---
id: workflow.troubleshooting.imports-and-mapping
title: Case imports and input mapping
summary: Uploaded Cases or external results do not match the selected input architecture or Case identities.
kind: error
product_area: troubleshooting
status: stable
updated: 2026-11-11
canonical: /docs/troubleshooting/imports-and-mapping
---
# Case imports and input mapping
## Symptom
Uploaded Cases or external results do not match the selected input architecture or Case identities.
## Likely causes
| What you observe | Focused guide |
| --- | --- |
| Case fields or material mappings are rejected | [Case upload troubleshooting](/docs/troubleshooting/dataset-upload) |
| External responses do not join the immutable Case manifest | [Output mapping troubleshooting](/docs/troubleshooting/output-mapping) |
| Expected behavior is absent from the recorded Run | [Missing Outputs](/docs/troubleshooting/missing-outputs) |
## Fix
Check the Project Input Schema for Case imports and the selected Benchmark Version manifest for output imports. Preserve issued Case IDs. Repair the source rows or mapping through the owning upload workflow.
Follow the focused guide for the actual state you observe; keep accepted records and explicit human decisions intact.
## Prevention
Preserve exact object and version identities, review the relevant source context, and inspect the accepted state before comparing outcomes.
## Related task pages
{% related-card-grid title="Return to the workflow" %}
- [Complete your first alignment loop](/docs/quickstart)
{% /related-card-grid %}
## Related reference pages
{% related-card-grid title="Diagnose the observed state" %}
- [Case upload troubleshooting](/docs/troubleshooting/dataset-upload)
- [Output mapping troubleshooting](/docs/troubleshooting/output-mapping)
- [Missing Outputs](/docs/troubleshooting/missing-outputs)
{% /related-card-grid %}
---
id: troubleshooting.dataset-upload
title: Case upload troubleshooting
summary: Repair uploads with rejected rows, missing inputs, incorrect column mapping, or Cases that arrive without usable context.
kind: error
product_area: troubleshooting
status: stable
updated: 2026-11-06
canonical: /docs/troubleshooting/dataset-upload
---
# Case upload troubleshooting
## Symptoms
- The file is rejected before column mapping.
- Required input fields are absent or cannot be selected.
- The preview puts outputs, metadata, or conversation context in the wrong fields.
- The upload completes but expected Cases are not visible in the Case Pool.
- Imported Cases are visible but cannot be reviewed or classified reliably.
## Likely causes
- The source file has unusable headers, duplicate columns, or blank input rows.
- Required Case input is unmapped or mapped from the wrong column.
- Conversation context, output identity, or metadata was flattened into the wrong field.
- The import completed, but the operator expected candidate Cases to become Benchmark members automatically.
## Diagnose the upload in order
1. Confirm the selected file is the intended source and uses a supported tabular shape for the upload surface.
2. Inspect headers and several real rows outside Teammately. Remove blank header rows, merged presentation cells, duplicate column names, and records that contain no usable input.
3. Return to **Map columns**. Map the Case input first, then candidate or reference output only when that identity is known. Map contextual columns as context or metadata rather than concatenating them into the input.
4. Review the preview for nulls, truncated objects, serialized JSON, and swapped user/assistant fields.
5. Submit a small representative file before importing the whole source.
6. After completion, open the Case Pool and verify row counts, a simple Case, a boundary Case, a conversation Case, and a row with missing optional data.
## Fix
- **No required input:** choose the correct input column or add a normalized input field to the source file.
- **Conversation collapsed into text:** preserve the structured turn context supported by the Project instead of guessing a public conversation schema.
- **Output mapped as input:** correct the mapping and re-upload; preserve the Case versions captured by existing Snapshots.
- **Missing context:** map supporting columns, then decide whether the existing imported Cases should be superseded or retained as an identifiable attempt.
- **Duplicate Cases:** compare stable source identifiers and Case content before adding candidates to a Benchmark.
## Prevention
Keep an untouched source file, a documented mapping decision, and a small QA sample. Treat database or internal representation details as implementation, not as the upload contract. The product preview is the last checkpoint before rows become Case Pool candidates.
{% example-demo title="Example: transcripts import without account tier" %}
The upload succeeds, but reviewers cannot explain why enterprise exceptions apply. The operator finds that `account_tier` was left unmapped. They add it as context, re-upload a representative sample, confirm the field in Case presentation, and only then import the full set. The incomplete candidates are not added to a Benchmark.
{% /example-demo %}
## Related task pages
{% related-card-grid title="Related workflows" %}
- [Import and prepare cases](/docs/operating-manual/import-and-prepare-cases)
- [Case Pool](/docs/coverage-engineering/case-pool)
- [Metadata and context](/docs/reference/metadata-and-context)
- [Unclear Cases](/docs/troubleshooting/unclear-cases)
{% /related-card-grid %}
## Related reference pages
{% related-card-grid title="Related reference" %}
- [Cases](/docs/object-model/cases)
- [Case Pool surface](/docs/object-model/case-pool)
- [Metadata and context](/docs/reference/metadata-and-context)
{% /related-card-grid %}
---
id: troubleshooting.output-mapping
title: Output mapping troubleshooting
summary: Fix external output rows that do not join cleanly to immutable Case IDs in an output-only Run.
kind: error
product_area: troubleshooting
status: stable
updated: 2026-11-06
canonical: /docs/troubleshooting/output-mapping
---
# Output mapping troubleshooting
Use this when externally produced responses exist but the mapping preview cannot join them cleanly to the Cases in the selected Benchmark Version.
## Symptom
Rows are unmatched, duplicated, or mapped to the wrong Case ID, or the wrong column was selected as the response. No output-only Run should be trusted until the mapping preview is correct.
## Likely causes
- External rows use row order or display text instead of immutable Case IDs.
- The file contains Case IDs from another Benchmark Version or Dataset export.
- The selected response column or identifier column is wrong.
- Several candidate output sets were combined without distinct metadata.
## Diagnostic checks
- Compare several affected case IDs with the output source IDs.
- Check whether the output set has candidate metadata such as model, prompt, retrieval version, or run identity.
- Confirm the source file was produced from the same immutable Case population.
- Inspect duplicate, blank, and unknown identifier counts in the mapping preview.
## Fix
- Correct the external file and map using immutable Case IDs rather than row position.
- Select the intended response column and keep one candidate output set per output-only Run.
- Create a new output-only Run from the corrected mapping. Existing Runs retain their original mapping.
- Repair missing Case context through the Case workflow, not during output mapping; create a new version boundary when Case content changes.
## Prevention
- Preserve source IDs through import and output generation.
- Sample mapped outputs before expert contribution work and before Evaluation Runs.
- Keep candidate identity in run metadata.
- Treat each imported output-only Run as a record of the submitted responses; it is not a saved Harness Version.
## Related task pages
{% related-card-grid title="Related task pages" %}
- [Import and prepare cases](/docs/operating-manual/import-and-prepare-cases)
- [Import External Evaluation Outputs](/docs/benchmark-evaluations/output-mapping)
- [Inspect Evaluation Results](/docs/benchmark-evaluations/inspect-results)
{% /related-card-grid %}
## Related reference pages
{% related-card-grid title="Related reference pages" %}
- [Outputs](/docs/object-model/outputs)
- [Represent conversations in Cases](/docs/object-model/represent-conversations-in-cases)
- [Benchmark Evaluations](/docs/benchmark-evaluations)
{% /related-card-grid %}
---
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-11-06
canonical: /docs/troubleshooting/missing-outputs
---
# Missing Outputs
Use this when an Evaluation Run has no response for an intended Case. First identify whether the response was expected 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, planned Trials, and failed Cases. For managed execution, confirm the selected Harness Version; for imported results, confirm the external candidate context.
- 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 under unchanged conditions, use **Run again** when an independent execution is intended. **Run evaluation** reopens matching existing work, including a failed Run.
- If the Harness changes, publish the corrected saved Version and select it through **Run evaluation**. Preserve the intended Benchmark Version and review the resulting execution conditions.
- For imported outputs, append only missing Cases to an uncompleted Trial using immutable Case IDs. Correcting an accepted response or adding Cases after completion requires a new Trial in the external Run or a new Run. Preserve the original results and explicitly confirm partial completion when Cases remain absent.
- 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.
A repeated Run retains its own history and does not silently replace the Run marked **Used for score**. See [Run a Benchmark Evaluation](/docs/benchmark-evaluations/run-evaluation#reuse-and-deliberate-repeats) for reuse and deliberate repetition.
## 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 Evaluation](/docs/benchmark-evaluations/run-evaluation)
- [Import External Evaluation Outputs](/docs/benchmark-evaluations/output-mapping)
{% /related-card-grid %}
## Related reference pages
{% related-card-grid title="Related reference pages" %}
- [Outputs](/docs/object-model/outputs)
- [Cases](/docs/assets/cases)
- [Benchmarks](/docs/object-model/benchmarks)
{% /related-card-grid %}