> For the complete documentation index, see [llms.txt](https://docs.konnekt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konnekt.io/es/troubleshooting/what-is-the-maximum-path-and-file-name-length.md).

# ¿Cuál es la longitud máxima de la ruta y del nombre de archivo?

KONNEKT tiene que respetar los límites de longitud de la ruta y del nombre de archivo de ambos mundos:

* **SharePoint Online**\
  y
* **Windows**.

La longitud máxima de un nombre de archivo incluyendo la ruta es **260 caracteres** en total.

Consta de ruta y nombre de archivo:

* **ruta** es: `\\onedrive-<yourTenant>\<site>\<library>\<foldernames>\`\
  Está limitado a 248 caracteres.
* **nombre de archivo** es: `<name>.<extension>`\
  Siempre se reservan 12 caracteres para el nombre de archivo (8.3). La ruta y el nombre de archivo juntos no deben exceder el límite de 260 caracteres en total.

Estos límites se deben principalmente a las restricciones del sistema operativo Windows y del Explorador de archivos. Los detalles se pueden encontrar [aquí](https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=cmd).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.konnekt.io/es/troubleshooting/what-is-the-maximum-path-and-file-name-length.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.