> For the complete documentation index, see [llms.txt](https://docs.fylr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fylr.io/for-system-administrators/symptom-and-solution/log-messages-that-can-be-ignored.md).
# Log messages that can be ignored
```
WRN Invalid token: "" BackendID=SyzRaj Env=api RunID=ANibqg path=/api/v1/user/session query=access_token=ory_at_CCS... status=400
```
... and ...
```
WRN Accepting token failed error
```
... are probably just old browser sessions with a now invalid authentication.
### During migration
```
level=warning msg="Request failed after 29ms: Status not OK but \"400 Bad Request\" [400] fylr error: \"Duplicate file reference provided: www.easydb.example.com:eas:12345:original with file id 67890\" [EasDuplicateReference]"
```
... This happens if the same asset is linked in several versions in one object. In this case, the asset should not be uploaded multiple times. Instead, the same asset ID is used again in all versions. This is only logged because it is recognized as an error in a central location (API error with status code 400), but it is then evaluated by fylr restore and not treated as an actual error.
### More ignorable messages without explanation:
```
could not obtain lock on row in relation
```
```
WRN Unknown endpoint method GET /api/v1/plugin/mapbox-gl.js.map BackendID=SyzRaj Env=api RunID=YOYZCz path=/api/v1/plugin/mapbox-gl.js.map query= status=400
```
```
WRN Error occurred in NewIntrospectionRequest error=request_unauthorized Env=api
```
```
WRN Copying html for plugin error=": unable to load: 404 Not Found" BackendID=SyzRaj Env=api RunID=kYTPGF
```
```
WRN Copying html for plugin error=": unable to load: 404 Not Found" BackendID=SyzRaj Env=api RunID=kYTPGF
```
```
DBG Console stream socket message error="websocket: close 1006 (abnormal closure): unexpected EOF" BackendID=SyzRaj Env=api RunID=aZRkCt
```
---
# 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://docs.fylr.io/for-system-administrators/symptom-and-solution/log-messages-that-can-be-ignored.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.