# Page Not Found

The URL `2024-7/07.17` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [07.17 멀티 파이프라인](https://recatch.gitbook.io/releasenotes/updates/2024/2024-7/07.17.md)
- [09.12 리캐치 내 사용 가이드 배치](https://recatch.gitbook.io/releasenotes/updates/2024/2024-9/09.12.md)
- [09.10 로그인 - 이메일 계정 확장](https://recatch.gitbook.io/releasenotes/updates/2024/2024-9/09.10.md)
- [08.27 워크플로우 복제](https://recatch.gitbook.io/releasenotes/updates/2024/2024-8/08.27.md)
- [08.07 워크플로우 - 폼 사용성 개선](https://recatch.gitbook.io/releasenotes/updates/2024/2024-8/08.07.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://recatch.gitbook.io/releasenotes/updates/2024/2024-7/07.17.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://recatch.gitbook.io/releasenotes/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://recatch.gitbook.io/releasenotes/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., `/releasenotes/updates/2024/2024-7/07.17.md`).

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