The stale confirmation

Profile updates return success, but the confirmation read sometimes shows the previous value when replica lag is present.

Initial failing signalconfirmation reads from the replicaExpected behavior: A confirmation read after an update uses the primary. · actual behavior: The confirmation read uses the replica instead.

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Compare an ordinary profile read with the confirmation read after an update.
Trace how each operation selects a read target.
Restore read-after-write consistency without moving all traffic to the primary.

Focus Mode

Start

src/readTarget.js

Likely area

src/readTarget.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicDatabases & Consistency

DifficultyMedium

Est. time18 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace