---
id: OV-C9-POS-003
title: "Non-PJP multi-device: both submissions persist as separate records"
product: mobile
module: offline-visitation
type: integration
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK144
  tsdSection: C9
  tsdScenario: C9.3
  prd: PK144
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK144 TSD C9.3; pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-OV-logged-in-online
tags:
  - mobile
  - offline-visitation
  - sync
  - pk144
  - staging
---
## Objective
Verify Non-PJP re-visits from two devices both record as separate visitations.

## Preconditions
- See [[PRE-OV-logged-in-online]]
- And a Non-PJP employee uses the same account on Device A and Device B

## Steps
1. Device A completes a visitation online (backend records it)
2. Device B holds a separately-initiated visitation for the same channel, then reconnects and syncs

## Expected Result
- Then the backend records Device B as a NEW visitation record
- And re-visits are permitted for Non-PJP — no rejection
- And both visits appear in Riwayat

## Source Traceability
- TSD: PK144
- Section: C9 - Multi-device Race Conditions
- Scenario: C9.3 - Non-PJP multi-device: both submissions succeed
- Acceptance Criteria: E8.US-5 AC2

## Evidence Required
- Backend records and Riwayat showing both visits.

## Notes / Gaps
- Testing Concern #36 (Note): 2-device test environment setup required.