# Page Not Found

The URL `files/fz8kwDZcZhbIwxwkhEfo` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [FAQs & Troubleshooting](https://cnsonline.gitbook.io/cargoes-community/export-lite/faqs-and-troubleshooting.md)
- [The Dashboard](https://cnsonline.gitbook.io/cargoes-community/export-lite/introduction/navigating-export-lite/the-dashboard.md)
- [Introduction to Export Lite](https://cnsonline.gitbook.io/cargoes-community/export-lite/introduction/introduction-to-export-lite.md)
- [Search Scheduled Reports](https://cnsonline.gitbook.io/cargoes-community/export-lite/reports/search-scheduled-reports.md)
- [Search UCR via Export Voyage](https://cnsonline.gitbook.io/cargoes-community/export-lite/ucr/ucr-search/search-ucr-via-export-voyage.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://cnsonline.gitbook.io/cargoes-community/export-lite/faqs-and-troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://cnsonline.gitbook.io/cargoes-community/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://cnsonline.gitbook.io/cargoes-community/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/cargoes-community/export-lite/faqs-and-troubleshooting.md`).

You may also use `Accept: text/markdown` header for content negotiation.