---
id: OV-C6-POS-009
title: "Stored failure reason overwritten (not appended) on repeat failure"
product: mobile
module: offline-visitation
type: functional
priority: P2
risk: medium
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK144
  tsdSection: C6
  tsdScenario: C6.7
  prd: PK144
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK144 TSD C6.7; pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-OV-gagal-kirim-has-items
tags:
  - mobile
  - offline-visitation
  - perlu-dikirim
  - pk144
  - staging
---
## Objective
Verify only the most recent failure reason is retained on repeated failures.

## Preconditions
- See [[PRE-OV-gagal-kirim-has-items]]
- And an item already has a stored failure reason

## Steps
1. When a later resync attempt fails for a different reason

## Expected Result
- Then the stored reason is REPLACED (not appended)
- And historical failure reasons are NOT retained in this scope

## Source Traceability
- TSD: PK144
- Section: C6 - Modification & Resync
- Scenario: C6.7 - Failure reason overwritten on repeat failure
- Acceptance Criteria: M.31 AC6 scope notes

## Evidence Required
- Stored reason before/after the second failure.

## Notes / Gaps
- Testing Concern #25 (Note): failure history audit log is out of scope.