> For the complete documentation index, see [llms.txt](https://tracer.gitbook.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tracer.gitbook.io/manual/support/troubleshooting/empty-score-and-link-files.md).
# Empty score and link files
It might happen that TRACER runs a detection successfully but produces empty `.link` and `.score` files. There are two potential reasons for this:
1. You might have the wrong value in the *Linking* implementation property: `INTER` instead of `INTRA` corpus linking:
``
1. Your ID numbering might be incorrect. Again, in the *Linking* section of the configuration file, you’ll notice the following property:
``
The value is set to a 7-digit ID. This means that your IDs should be 7-digits long. If you would rather work with shorter digits, you must change this value in the configuration file accordingly. If possible, please avoid using IDs above 2.000.000, as these require extra steps in order to be processed.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://tracer.gitbook.io/manual/support/troubleshooting/empty-score-and-link-files.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.