{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T22:44:07.049Z",
  "record_id": "VXI-EXT-PROCUREMENT-SERVICEBUS-SETTLEMENT-FAILURE-01-v1",
  "record_kind": "external_reference",
  "title": "Service Bus: Failed settlement after completed work",
  "system": "Azure Service Bus",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "If Service Bus Complete fails after processing, does that mean the agent action failed too?",
  "near_questions": [
    "Can Service Bus Complete fail after the work succeeds?",
    "Does MessageLockLost prove the action was not performed?",
    "What should be retained before settling a Service Bus message?",
    "Which result belongs to the redelivered Service Bus job?",
    "Was the business write committed before Complete?",
    "Can a broken connection make settlement uncertain?",
    "How is duplicate processing avoided after a failed Complete?",
    "Is broker settlement the same as business completion?",
    "Which lock applied to the failed settlement?",
    "What evidence resolves Service Bus acknowledgement uncertainty?",
    "Should a completed job be rerun after settlement failure?",
    "Can INDEX settle Service Bus messages?"
  ],
  "supported_claims": [
    {
      "claim": "Service Bus Complete can fail because of a network problem, expired lock or service condition after the handler has already done its work. The message may be redelivered, so the application must decide how to preserve and recognize an existing result. Broker settlement failure is not proof that the business effect did not occur.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Atomicity between message settlement and external writes or verified broker state",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "Service Bus Complete can fail because of a network problem, expired lock or service condition after the handler has already done its work. The message may be redelivered, so the application must decide how to preserve and recognize an existing result. Broker settlement failure is not proof that the business effect did not occur.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Azure Service Bus: Transfers, locks and settlement",
    "source_url": "https://learn.microsoft.com/en-us/azure/service-bus-messaging/message-transfers-locks-settlement",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SERVICEBUS-SETTLEMENT-FAILURE-01-v1",
    "candidate_record_sha256": "2c3160f68189ad90bbc8d0d57917b3e485f4e9de8d525b0b83b60fad09cf7f31",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "Service Bus Complete can fail because of a network problem, expired lock or service condition after the handler has already done its work. The message may be redelivered, so the application must decide how to preserve and recognize an existing result. Broker settlement failure is not proof that the business effect did not occur.",
    "required_buyer_context": "Message ID, lock history and exact Complete failure. Business-result record and external effect observed before settlement. Redelivery handling and reconciliation keyed to the original action. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-17",
    "claim_to_check": "If Service Bus Complete fails after processing, does that mean the agent action failed too?",
    "documented_statement": {
      "status": "documented",
      "statement": "Service Bus Complete can fail because of a network problem, expired lock or service condition after the handler has already done its work. The message may be redelivered, so the application must decide how to preserve and recognize an existing result. Broker settlement failure is not proof that the business effect did not occur.",
      "source_ids": [
        "servicebus-settle"
      ]
    },
    "buyer_evidence_required": [
      "Message ID, lock history and exact Complete failure.",
      "Business-result record and external effect observed before settlement.",
      "Redelivery handling and reconciliation keyed to the original action."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline a safe-repeat conclusion until prior business completion and settlement uncertainty are separated."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "servicebus-settle",
        "url": "https://learn.microsoft.com/en-us/azure/service-bus-messaging/message-transfers-locks-settlement",
        "final_url": "https://learn.microsoft.com/en-us/azure/service-bus-messaging/message-transfers-locks-settlement",
        "title": "Azure Service Bus: Transfers, locks and settlement",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T22:37:23.358Z",
        "version_context": "Rolling Service Bus guide; PeekLock settlement failures",
        "sha256": "06b38ff51df77712d08ffeef27ea08afb31391288a5b24d20e1c6c8207195acc",
        "bytes": 63201,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Settling receive operations; PeekLock"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Repeating a completed effect to repair a failed acknowledgement can duplicate an external action.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Message ID, lock history and exact Complete failure. Business-result record and external effect observed before settlement. Redelivery handling and reconciliation keyed to the original action."
    },
    "buyer_relevance": "Repeating a completed effect to repair a failed acknowledgement can duplicate an external action.",
    "refusal_conditions": [
      "Decline a safe-repeat conclusion until prior business completion and settlement uncertainty are separated."
    ]
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#servicebus-complete-failure-committed-work",
  "machine_readable_record": "/varexis-index/records/servicebus-complete-failure-committed-work.json"
}
