Repair Android WorkManager Constraint Retry Storm

Repair Android WorkManager Constraint Retry Storm — EVIDENCE-LIMITED REVIEW

Scenario received

An upload worker retries repeatedly when a phone transitions between Wi Fi and battery saver.

Evidence inventory

• S1: WorkManager scheduling code — partial extract described by the requester; original full source not provided here.
• S2: worker run result logs — partial extract described by the requester; original full source not provided here.
• S3: device power and network events — NOT PROVIDED; required to validate dependent findings.
• S4: backoff policy settings — NOT PROVIDED; required to validate dependent findings.

Case-specific checks

Align constraint changes with retries. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
2.

Distinguish cancellation and retry results. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
3.

Inspect unique work policies. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
4.

Test bounded recovery on device states. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.

Deliverables

Work retry causality map. Create an evidence-linked section with observations, missing data, owner and next validation step.

Worker lifecycle patch. Create an evidence-linked section with observations, missing data, owner and next validation step.

Device state test matrix. Create an evidence-linked section with observations, missing data, owner and next validation step.

Acceptance gate

The repair preserves intended offline queuing without runaway retry or duplicate upload. Do not label this gate passed until supplied source records actually demonstrate it.

Verdict and next action

INCOMPLETE — evidence required. Request S3 and S4 from the authorized owner, reconcile them with S1 and S2, then repeat the four checks and log remaining conflicts. No production change, approval, communication, or test run is claimed.