# HELP_TOPIC_NOT_FOUND — help topic not found

Returned by `GET {ContextPath}/help/{topic}` when `{topic}` is well-formed (matches `[A-Za-z0-9._-]+`) but does not resolve to any topic in the tree. Clie…

<em>cyoda-go version <a href="https://github.com/Cyoda-platform/cyoda-go/releases/tag/v0.6.2">0.6.2</a></em>

# errors.HELP_TOPIC_NOT_FOUND

## NAME

HELP_TOPIC_NOT_FOUND — requested help topic does not exist.

## SYNOPSIS

HTTP: `404 Not Found`. Retryable: no.

## DESCRIPTION

Returned by `GET {ContextPath}/help/{topic}` when `{topic}` is well-formed (matches `[A-Za-z0-9._-]+`) but does not resolve to any topic in the tree. Clients should `GET {ContextPath}/help` to discover available topic paths.

## SEE ALSO

- errors

## See also

- [`cyoda help errors`](/help/errors/) — Every error response from the Cyoda REST API carries a structured `errorCode` in the `properties` object. Multiple codes may share the same HTTP status. Programmatic handling keys on `errorCode`, not HTTP status.

## Raw formats

- [`/help/errors/help_topic_not_found.json`](/help/errors/help_topic_not_found.json) — full descriptor (matches `GET /help/{topic}` envelope)
- [`/help/errors/help_topic_not_found.md`](/help/errors/help_topic_not_found.md) — body only