Retry the latest terminally failed search projection
POST/api/v1/documents/:document_id/search/retry
The authorized, same-origin recovery command is fenced by the current strong document revision. It keeps the canonical generation and original directly available while a durable projection job retries.
Request
Responses
- 202
- 400
- 401
- 403
- 404
- 409
- 412
- 421
- 422
- 428
- 503
The durable search retry was queued
Response Headers
Relative URL of the queued task, or the document when no task was needed
Minimum polling delay in seconds
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request syntax, headers, body, or validated input is malformed or invalid
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The opaque credential is absent, ambiguous, malformed, expired, revoked, or invalid
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The browser mutation did not originate from this application, or the authenticated member lacks the required permission
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The resource is unknown or outside the authenticated household scope
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request conflicts with the current resource, revision, lease, credential, or idempotency state
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The strong revision precondition is stale
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request authority or direct peer is outside the configured Jiandu ingress boundary
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The supplied bytes, filename, declared field value, or supported-content validation failed
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
Exactly one valid strong If-Match value is required
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
A required core dependency is unavailable; retry with bounded backoff
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.