---
id: OV-C9-NEG-004
title: "PJP multi-device: late sync rejected because target already achieved"
product: mobile
module: offline-visitation
type: negative
priority: P0
risk: critical
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK144
  tsdSection: C9
  tsdScenario: C9.4
  prd: PK144
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK144 TSD C9.4; pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-OV-logged-in-online
tags:
  - mobile
  - offline-visitation
  - sync
  - negative
  - pjp
  - perlu-dikirim
  - pk144
  - staging
---
## Objective
Verify a PJP single-use target rejects a later sync from a second device while keeping the failed item locally.

## Preconditions
- See [[PRE-OV-logged-in-online]]
- And a PJP employee has an account on Device A (online) + Device B (offline), PJP target = 1 visit (single-use)

## Steps
1. Device A completes online → target achieved on backend
2. Device B (offline) attempts to sync the same visitation later

## Expected Result
- Then the sync FAILS with reason "Target already achieved via Device A"
- And the item is kept in Device B's Gagal Kirim queue (Gagal Terkirim) with standard 1-day retention
- And manual delete via "Hapus Draf" is allowed
- And manual "Kirim Ulang" is allowed but continues to fail

## Source Traceability
- TSD: PK144
- Section: C9 - Multi-device Race Conditions
- Scenario: C9.4 - PJP multi-device: sync rejected, target achieved
- Acceptance Criteria: E8.US-5 AC3

## Evidence Required
- Backend rejection reason; Device B queue state.

## Notes / Gaps
- No gap.