---
id: OV-C6-POS-002
title: "Failed sync detail page shows status, data, and plain-language reason"
product: mobile
module: offline-visitation
type: functional
priority: P1
risk: medium
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK144
  tsdSection: C6
  tsdScenario: C6.2
  prd: PK144
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK144 TSD C6.2; 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 the failed sync detail view content and the Aktivitas correction indicator.

## Preconditions
- See [[PRE-OV-gagal-kirim-has-items]]
- And a "Gagal Terkirim" item exists

## Steps
1. When the employee taps a "Gagal Terkirim" item from the list

## Expected Result
- Then Detail Kunjungan opens showing failed status clearly, channel info + photos, check-in/check-out timestamps & coordinates, the assigned task list and submitted form data, the failure reason in plain Bahasa Indonesia, and available actions per status + failure type
- And the failed activity in Aktivitas is marked with a failed/invalid indicator and the row shows correction required

## Source Traceability
- TSD: PK144
- Section: C6 - Failed Sync Detail
- Scenario: C6.2 - View failed sync detail
- Acceptance Criteria: M.29 AC1–AC4

## Evidence Required
- Screenshot of the failed detail page and Aktivitas row.

## Notes / Gaps
- Testing Concern #24 (High): plain-language failure copy mapping.