---
id: OV-C10-EDGE-003
title: "Force-quit during form filling preserves the in-progress draft"
product: mobile
module: offline-visitation
type: recovery
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK144
  tsdSection: C10
  tsdScenario: C10.1
  prd: PK144
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK144 TSD C10.1 (form branch); pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-OV-mode-luring-active
tags:
  - mobile
  - offline-visitation
  - mode-luring
  - edge-case
  - pk144
  - staging
---
## Objective
Verify force-quitting while filling a form keeps the in-progress draft recoverable.

## Preconditions
- See [[PRE-OV-mode-luring-active]]
- And a visitation is "Dalam Proses" with a form being filled

## Steps
1. Force-quit during form filling, then relaunch

## Expected Result
- Then the in-progress draft (Dalam Proses) is still available in "Aktivitas"
- And data is preserved up to the last auto-save point
- And drafts respect end-of-day retention

## Source Traceability
- TSD: PK144
- Section: C10 - Cross-cutting Edge Cases & Failure Recovery
- Scenario: C10.1 - Force-quit recovery: clean state
- Acceptance Criteria: E11.US-1 AC1–AC4

## Evidence Required
- Aktivitas draft recovery after relaunch.

## Notes / Gaps
- Testing Concern #37 (cross-ref C2 #12): auto-save cadence determines the recovery point.