Skip to main content
GET
Get the latest knowledge re-embed run
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.

v2 compatibility notes

GET /api/v2/knowledge/reembed/getLatestRun returns { latestRun }: the newest re-embed run, whatever its status, or null before the first. It needs knowledge:read. It is the run the reembed section of knowledge health reports. MCP hosts call it through forge_call_operation with operationId getLatestKnowledgeReembedRun. A run carries its status (running, completed or failed), targetModelId and targetDimension, startedAt and finishedAt, namespacesTotal and namespacesDone, entriesReembedded, entriesSkipped and entriesFailed, and failedInReadable: how many of its failed rows are in the caller’s readable namespaces. A run is deployment-wide, so its error text and who started it are never returned (the error may name another tenant’s namespace); hasError says it failed with one. The route takes no query parameter; any one answers 400 bad_request. Start a run with Start a knowledge re-embed.

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Response

The newest re-embed run

data
object
required

The newest re-embed run, whatever its status, or null before the first: its progress counts, and how many of its failed rows are in the caller's readable namespaces. Its error text and starter are never returned; hasError says it failed with one.

meta
object
required