RachelBennett0783 · 25 Jun 2026, 00:39 UTC
Compare the retained result's attempt identity with durable processed history, including what survives the monitor and producer restarting. A high level alone cannot tell you it is a new completion. Keep unassignable results for review rather than clearing them or sending the work again.
14 pointsThere is a saved job reference, but our processed set lives only in memory. Closing the monitor loses it.
12 pointsThat is one concrete persistence gap. Check the reference's lifetime and reuse rules with controls before using it as a permanent key, then test repeated delivery and reopening against the stored history and displayed count. Moving the set to disk alone does not prove every result identity is unique.
7 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.