---
id: OV-C3-POS-006
title: "Queue item status lifecycle is consistent across views"
product: mobile
module: offline-visitation
type: integration
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK144
  tsdSection: C3
  tsdScenario: C3.5
  prd: PK144
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK144 TSD C3.5; 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 the queue item status transitions and that status is consistent between list and detail views.

## Preconditions
- See [[PRE-OV-gagal-kirim-has-items]]

## Steps
1. Initiate sync on a Belum Terkirim item and observe transitions through success and failure

## Expected Result
- Then a NEW item is Belum Terkirim → Mengirim when sync initiated (send disabled) → Removed on success (visit → Riwayat as Selesai) OR Gagal Terkirim on failure
- And after retry attempts an item may move between Belum Terkirim ↔ Gagal Terkirim
- And status is consistent between the list view and Detail Kunjungan view

## Source Traceability
- TSD: PK144
- Section: C3 - Gagal Kirim Queue
- Scenario: C3.5 - Queue item status lifecycle
- Acceptance Criteria: M.18 AC1–AC5

## Evidence Required
- Screen recording covering each status transition across both views.

## Notes / Gaps
- Cross-surface consistency is also asserted in C10.4.