---
id: OV-C9-POS-006
title: "Multi-device failures follow non-blocking silent retry with clear reason"
product: mobile
module: offline-visitation
type: functional
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK144
  tsdSection: C9
  tsdScenario: C9.6
  prd: PK144
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK144 TSD C9.6; 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
  - sync
  - pk144
  - staging
---
## Objective
Verify user-facing behavior for multi-device failure cases is non-blocking and explained.

## Preconditions
- See [[PRE-OV-gagal-kirim-has-items]]
- And a multi-device failure has occurred

## Steps
1. Observe queue and detail behavior after a multi-device failure

## Expected Result
- Then the Device B item is kept in Gagal Kirim (Gagal Terkirim) with standard 1-day retention, manual "Hapus Draf" allowed, and manual "Kirim Ulang" allowed but expected to fail
- And there is NO special error UI; the existing non-blocking silent retry policy is followed
- And the user sees the item in the queue (not blocked) and the detail page failure reason explains the cause (non-fixable)

## Source Traceability
- TSD: PK144
- Section: C9 - Multi-device Race Conditions
- Scenario: C9.6 - Failure handling & user-facing behavior
- Acceptance Criteria: E8.US-5 AC6, AC7

## Evidence Required
- Queue + detail screenshots for a multi-device failure.

## Notes / Gaps
- No gap.