---
title: "Find out why related-code search could not select any input | Proofline Help"
description: "If an assessment carried no related code, read its reason under Configuration and preferences → Related code before treating the absence as evidence that no related code exists."
url: https://proofline.sh/help/assessment-diagnose-unavailable-code-index/
---

[Help center](/help/)

# Find out why related-code search could not select any input

If an assessment carried no related code, read its reason under **Configuration and preferences → Related code** before treating the absence as evidence that no related code exists.

## Identify the missing input

An unavailable code index, unavailable semantic index and unavailable repository source each identify a different missing input. Other reasons say the change had too many changed definitions or a search query was too long. Record the reason shown for the specific environment and run.

An assessment that kept no related-code record says so. A completed search with no candidate locations may leave this row out. Neither gives you a list of files that were inspected.

## Related guides

-   [Inspect the inputs behind an environment assessment](/help/inspect-an-environment-assessments-recorded-inputs/)
-   [Read a review](/help/read-review/)
