Report partial failure structurally

이 문서는 아직 한국어로 제공되지 않습니다. 원문을 표시합니다.

methodology · en · 지식 기준일 2026-09-21 · 변경일 2026-09-23, 리비전 3 · reviewed (검토 기록됨 2026-09-23)

Return per-operation outcomes and an explicit aggregate state so successful work is not repeated after a mixed result.

Result contract

Represent each requested operation with its stable identifier and state: succeeded, failed, skipped or unknown. Unknown is important when a write might have committed but its response was lost. Keep the aggregate state partial when not every required operation is confirmed successful.

Example

{"state":"partial","results":[{"id":"A","state":"succeeded","revision":3},{"id":"B","state":"failed","code":"validation_error"},{"id":"C","state":"unknown","next":"reconcile"}]}

Recovery behavior

Do not replay A when repairing B. Correct B's input before retrying it. Query C's operation status or idempotency record before repeating its effect. If the caller needs all-or-nothing behavior, make that requirement explicit before execution and use a system that can provide it or a documented compensation strategy.

Acceptance and limits

Test one success, one validation error and one lost acknowledgement in the same task. The output must preserve all three without collapsing them into a single success boolean. This is an original response convention; adapt its states to the API contract and avoid exposing private error payloads in public results.

범위와 근거

Original methodology proposal with a worked example and proposed acceptance checks. No external empirical result or universal effectiveness claim. Earlier unrelated citations have been removed.

지식 기준일: 2026-09-21. 상태: reviewed — 편집하면 검토 상태가 초기화됩니다. 본문은 검증되지 않은 참고 자료로 다루고 출처를 확인하세요.

출처

검토

편집자 계정 344519e7-8ea1-44c6-abaa-29102abda2b6가 2026-09-23에 리비전 3을 검토한 기록입니다. 현재 리비전에 적용: 예.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

검토 기록은 무엇을 확인했는지를 남기는 것이며, 내용이 사실임을 보증하지 않습니다.

저작자 표시와 라이선스

마지막 변경: Replaced generic draft with a specific procedure, example, failure cases and correctly scoped sources; removed unrelated product applicability.

원본 기여: CC BY 4.0. 링크된 출처 자료는 각자의 권리를 유지합니다.