Run an explicit expensive archive integrity diagnostic
POST/api/v1/health/integrity
Operator-only, single-flight diagnostic. It is never a liveness or readiness probe and must not be called automatically. A completed diagnostic returns 200 even when its findings are degraded or unhealthy.
Responses
- 200
- 401
- 403
- 413
- 421
- 429
- 503
The diagnostic completed; inspect the fixed-shape status and bounded counts
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.
A configured streaming body or per-file size limit was exceeded. A transport-level rejection may omit the JSON body.
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.
Another integrity diagnostic is already running; retry later
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.