OliverChan1059 · 1 Apr 2026, 07:40 UTC
Use an explicit delivery queue, then assert both stored attempts after the old completion arrives; preserve the original attempt identity instead of looking up whichever attempt is current.
6 pointsQueue added. Same sequence now fails every run. The event carries the old identity, but our lookup uses the current attempt for the job name.
7 pointsTest its genuine late completion against the old attempt, plus duplicate delivery and the new attempt's own result. The fix must preserve legitimate older evidence as well as protect the new state.
6 pointsHandler corrected in the offline build. Old result completes its own attempt, duplicate adds nothing, and the new attempt waits until its result arrives. Thanks, Farah, checking both rows caught more than watching the current tile.
14 pointsDoes the same identity handling survive reopening the application, or is part of the duplicate protection still only in memory?
13 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.