> 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/unable-to-parse-date.md).

# Unable to parse date

![](/files/-LAO3a6-Ifjo1tRg8UXm)

This error is caused by the presence of a sequence of characters or absence of text in the **second column** of the corpus file. The term `date` is misleading and does not, in this case, indicate that the problem is with dating information (which can be added in the third column of the corpus file). The problem here is that TRACER does not provide information about the specific issue with the text, so the user has to check the corpus file in a text editor and correct anything that might seem incorrect or problematic. In order to fix this error, the user has to correct, save and re-run TRACER. If the error persists, then more corpus cleaning is needed.


---

# 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/unable-to-parse-date.md?ask=<question>&goal=<endgoal>
```

`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.