Skip to main content
POST
Retry a stuck pending knowledge entry
Takes { "entryId": "<id>" } from the pending.entries of knowledge health and answers { entryId, scheduled }. The entry must be in the caller’s writable namespaces; an entry restricted to named people, a missing id and an entry outside the writable set answer 404. scheduled is false, and nothing is scheduled, for an entry that is no longer active or is already embedded. See Remedies.

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.

Headers

Idempotency-Key
string

1–255 printable ASCII characters. A repeat with the same key and request never runs the write again, a 5xx included. It returns the first response (Idempotency-Replayed: true) only when the route's current authorization policy permits disclosure; otherwise 409 idempotency_result_unavailable. Honoured for External App JWTs and platform and MCP keys; an External App's static companion key is not protected.

Required string length: 1 - 255

Path Parameters

entryId
string
required

The pending entry's id (pending.entries[].entryId in knowledge health).

Response

Retry scheduled (scheduled: true) or not needed (scheduled: false)

data
object
required

A pending-entry retry's outcome. scheduled: true: the entry is embedded again now. scheduled: false: the entry is no longer active or is already embedded, and nothing was scheduled.

meta
object
required