{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T12:55:40.483Z",
  "record_id": "VXI-EXT-PROCUREMENT-STEPFUNCTIONS-REDRIVE-01-v1",
  "record_kind": "external_reference",
  "title": "Step Functions redrive: Original execution identity",
  "system": "AWS Step Functions",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does redriving a failed workflow use the newly deployed fix?",
  "near_questions": [
    "Does Step Functions redrive follow an updated alias?",
    "Is the original execution ARN preserved?",
    "Are successful steps always started again?",
    "Which failed state resumes?",
    "Does redrive reuse the original input?",
    "Is this a Standard or Express workflow?",
    "Is the execution still eligible for redrive?",
    "Can a task have committed externally before failure?",
    "Which state-specific rules apply?",
    "When is a new execution a different operation?",
    "What evidence should an agent retain for recovery?",
    "Can I save the original-version redrive boundary?"
  ],
  "supported_claims": [
    {
      "claim": "Eligible Standard Workflow redrives retain the original execution identity, input and state-machine definition. Successful steps are generally preserved while failed work resumes according to state-specific rules. Updating an alias does not make a redrive use its new version; redrive and starting a new execution are different decisions.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "Eligible Standard Workflow redrives retain the original execution identity, input and state-machine definition. Successful steps are generally preserved while failed work resumes according to state-specific rules. Updating an alias does not make a redrive use its new version; redrive and starting a new execution are different decisions.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Step Functions execution redrive",
    "source_url": "https://docs.aws.amazon.com/step-functions/latest/dg/redrive-executions.html",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-STEPFUNCTIONS-REDRIVE-01-v1",
    "candidate_record_sha256": "e2041845c183d0cfbf34c8ec11f85464173c919fdf8daba2c7a7da11886f3579",
    "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": "Eligible Standard Workflow redrives retain the original execution identity, input and state-machine definition. Successful steps are generally preserved while failed work resumes according to state-specific rules. Updating an alias does not make a redrive use its new version; redrive and starting a new execution are different decisions.",
    "required_buyer_context": "Workflow type, original version, execution history, eligibility and external effects. Effective configuration and dated operational evidence have not been 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-16",
    "claim_to_check": "Redrive automatically picks up the latest workflow deployment.",
    "documented_statement": {
      "status": "documented",
      "statement": "Eligible Standard Workflow redrives retain the original execution identity, input and state-machine definition. Successful steps are generally preserved while failed work resumes according to state-specific rules. Updating an alias does not make a redrive use its new version; redrive and starting a new execution are different decisions.",
      "source_ids": [
        "step-redrive"
      ]
    },
    "buyer_evidence_required": [
      "Original execution version and input.",
      "Failure state and state-specific redrive behaviour.",
      "External side-effect and reconciliation evidence."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Check the original definition and prior side effects before approving recovery."
    },
    "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": "step-redrive",
        "url": "https://docs.aws.amazon.com/step-functions/latest/dg/redrive-executions.html",
        "final_url": "https://docs.aws.amazon.com/step-functions/latest/dg/redrive-executions.html",
        "title": "Step Functions execution redrive",
        "checked_on": "2026-10-16",
        "sha256": "430d779c297ed46d0a953fa3e7e61508470d2b0462e028bd151e5b6ddc68331f",
        "bytes": 34306
      }
    ],
    "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": "Save the recovery decision basis without implying that retrying applies a new software fix.",
      "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": "Workflow type, original version, execution history, eligibility and external effects."
    }
  },
  "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#step-functions-redrive-original-version",
  "machine_readable_record": "/varexis-index/records/step-functions-redrive-original-version.json"
}