方法路径摘要认证
GET/v1/cache-operation-requests/{idempotency_key}What the server did with a cache write sent with this Idempotency-Key登录会话

契约文件:api/control-cache-operations.openapi.yaml

接口详情

GET /v1/cache-operation-requests/{idempotency_key}

What the server did with a cache write sent with this Idempotency-Key

operationId
getTenantCacheWriteReceipt
认证
  • 登录会话:主控登录后的 Bearer 会话,由客户本人在自己的主控里使用;插件不能要求客户交出会话。
所需权限

全部需要:sites.read

说明(契约原文)

For a write whose response was lost (network, timeout, 5xx): accepted with the operation (the new one of a create or re-submit), or rejected with the error code the write was refused with. 404 means the server has no record of the key for the authenticated actor: the write was not received and may be sent again with the same key and body. Another actor's key is the same 404 (existence is never disclosed). Not-found and permission refusals of the write itself are not kept and also read as 404. Writes nothing.

参数

getTenantCacheWriteReceipt 参数
名称位置类型必填说明
idempotency_keypathstring是The Idempotency-Key the write was sent with (the batch key of a re-submit).
actionquerystring: create / retry / cancel / resubmit是—
operation_idquerystring(uuid)否The operation a retry, cancel or re-submit acts on; required for those, absent for create.
X-Request-IDheaderstring是—

响应

getTenantCacheWriteReceipt 响应
状态码说明
200The write was decided.

字段:status: string: accepted / rejected decided_at: string(date-time) operation?: object rejection?: object

400Invalid or non-canonical request.
401Authentication required.
403Exact cache permission is absent or route audience is wrong.
404Resource is absent or outside the effective tenant scope.
408Request context was cancelled or exceeded its deadline.
503A required store is unavailable; raw dependency errors are never returned.

失败时怎么办

  • 400 按字段说明修正参数或请求体再发;不要原样重试。
  • 401 检查凭据格式、是否过期或被轮换。
  • 403 检查 Key 范围与所有者当前权限、当前租户作用域;不要换更高权限账号绕过。
  • 404 资源不存在或不属于当前租户。
  • 503 依赖暂不可用:稍后用原 Idempotency-Key 重试。

↑ 回到列表