{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T17:54:06.066Z",
  "record_id": "VXI-EXT-PROCUREMENT-LAMBDA-SQS-PARTIAL-BATCH-01-v1",
  "record_kind": "external_reference",
  "title": "Lambda and SQS: Partial failures and repeated actions",
  "system": "AWS Lambda and SQS",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can one failed SQS batch item cause an agent to repeat actions that already succeeded?",
  "near_questions": [
    "Will Lambda retry successful messages from a failed SQS batch?",
    "Was ReportBatchItemFailures enabled?",
    "Which message identifiers were returned as failures?",
    "Did the function throw instead of returning partial results?",
    "Were successful business effects recorded before retry?",
    "How are unprocessed FIFO messages reported?",
    "Can batch retry duplicate an agent action?",
    "Does partial reporting prove exactly-once execution?",
    "What distinguishes a delivery ID from a business effect?",
    "Which batch items still need recovery?",
    "What evidence supports an Audit Coverage retry chain?",
    "Were completed and unprocessed items kept distinct?"
  ],
  "supported_claims": [
    {
      "claim": "By default, a failed Lambda SQS batch makes all its messages visible again, including successfully processed items. Partial reporting requires ReportBatchItemFailures plus the failed message identifiers. An uncaught function exception still fails the entire batch; FIFO handling also retains failed and unprocessed items after the first failure.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Exactly-once external effects or proof that partial reporting was configured correctly in the buyer deployment",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "By default, a failed Lambda SQS batch makes all its messages visible again, including successfully processed items. Partial reporting requires ReportBatchItemFailures plus the failed message identifiers. An uncaught function exception still fails the entire batch; FIFO handling also retains failed and unprocessed items after the first failure.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "AWS Lambda: Handling errors for an SQS event source",
    "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/services-sqs-errorhandling.html",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-LAMBDA-SQS-PARTIAL-BATCH-01-v1",
    "candidate_record_sha256": "f16059d56c74ec45f96c71d0a69e8ce97d44e83a829e14b16a13ec16a67b89bf",
    "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": "By default, a failed Lambda SQS batch makes all its messages visible again, including successfully processed items. Partial reporting requires ReportBatchItemFailures plus the failed message identifiers. An uncaught function exception still fails the entire batch; FIFO handling also retains failed and unprocessed items after the first failure.",
    "required_buyer_context": "Event-source mapping settings, queue type and message identifiers. Per-item outcomes and the returned batchItemFailures response or thrown exception. Business-effect identifiers and deduplication or reconciliation evidence for retries. 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": "Can one failed SQS batch item cause an agent to repeat actions that already succeeded?",
    "documented_statement": {
      "status": "documented",
      "statement": "By default, a failed Lambda SQS batch makes all its messages visible again, including successfully processed items. Partial reporting requires ReportBatchItemFailures plus the failed message identifiers. An uncaught function exception still fails the entire batch; FIFO handling also retains failed and unprocessed items after the first failure.",
      "source_ids": [
        "lambda-sqs-batch"
      ]
    },
    "buyer_evidence_required": [
      "Event-source mapping settings, queue type and message identifiers.",
      "Per-item outcomes and the returned batchItemFailures response or thrown exception.",
      "Business-effect identifiers and deduplication or reconciliation evidence for retries."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline once-only completion claims from a batch status alone; reconcile successful effects and the actual retry set before treating reprocessing as safe."
    },
    "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": "lambda-sqs-batch",
        "url": "https://docs.aws.amazon.com/lambda/latest/dg/services-sqs-errorhandling.html",
        "final_url": "https://docs.aws.amazon.com/lambda/latest/dg/services-sqs-errorhandling.html",
        "title": "AWS Lambda: Handling errors for an SQS event source",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T17:50:55.935Z",
        "version_context": "Rolling Lambda developer guide",
        "sha256": "5529f88b26167a60a6b65e8ae0bc936ac27dc84bda277032ddd5717baea06e64",
        "bytes": 46904,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Implementing partial batch responses"
        ]
      }
    ],
    "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": "An agent performing external changes needs item-level evidence before retrying a mixed-result batch, rather than counting each delivery as a new authorized 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": "Event-source mapping settings, queue type and message identifiers. Per-item outcomes and the returned batchItemFailures response or thrown exception. Business-effect identifiers and deduplication or reconciliation evidence for retries."
    },
    "buyer_relevance": "An agent performing external changes needs item-level evidence before retrying a mixed-result batch, rather than counting each delivery as a new authorized action.",
    "refusal_conditions": [
      "Decline once-only completion claims from a batch status alone; reconcile successful effects and the actual retry set before treating reprocessing as safe."
    ]
  },
  "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#lambda-sqs-partial-batch-retry-successful-items",
  "machine_readable_record": "/varexis-index/records/lambda-sqs-partial-batch-retry-successful-items.json"
}
