---
id: OV-C9-NEG-005
title: "Same visitation ID: sync rejected on backend status conflict"
product: mobile
module: offline-visitation
type: negative
priority: P0
risk: critical
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK144
  tsdSection: C9
  tsdScenario: C9.5
  prd: PK144
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK144 TSD C9.5; 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
  - pk144
  - staging
---
## Objective
Verify status-conflict rejection when the same visitation advances on another device.

## Preconditions
- See [[PRE-OV-logged-in-online]]
- And a visitation is already "Dalam Proses" on backend at Device B offline start
- And Device A completes/submits the SAME visitation online (backend status → Selesai)

## Steps
1. When Device B reconnects and syncs its offline submission

## Expected Result
- Then the sync FAILS with reason "Visitation status moved past expected state"
- And this applies REGARDLESS of whether the form has a visitation target
- And for a compound failure (same visitation ID + form target), both status-conflict and target-achievement reasons apply, though the sync would already fail on status conflict alone

## Source Traceability
- TSD: PK144
- Section: C9 - Multi-device Race Conditions
- Scenario: C9.5 - Same visitation ID: status conflict rejection
- Acceptance Criteria: E8.US-5 AC4, AC5

## Evidence Required
- Backend rejection reason for the status conflict.

## Notes / Gaps
- No gap.