I'm separating unsubmitted coupon checks from submitted checks with no known outcome. The old startup helper resends both. We already know reused labels make reconciliation worse; what should the new queue require before anything uncertain leaves review?
Our reconciliation discussion needed a named decision owner as well as distinct states; who can judge the retained evidence for an uncertain attempt, and what happens when that evidence cannot identify its outcome?
Quality with the application maintainer. Unknown entries stay outside automatic submission. We're attaching the available request identity and evidence, not matching on the current display label
Does a later matching result enter the review without automatically releasing the coupon? Receiving useful evidence and authorising its disposition should remain separate steps in the implementation.
It didn't. Late result set accepted directly. Author has removed that shortcut; evidence now attaches to the original attempt and waits for the defined disposition decision
Does that review state survive another restart, including one while the evidence is being saved? I'd want the reason still visible to whoever covers the next shift.
Second-restart test passes, interrupted evidence-save test doesn't. It loses the review reason, though it no longer resends. Still a bug, not calling the empty warning an improvement
Thank you for distinguishing those results. Include first startup with no usable evidence too; the page needs to explain that condition without borrowing a reason from the previous displayed coupon.
Reason persistence corrected. Missing-evidence startup, interrupted save and repeated late-result tests pass. Original uncertain coupon still lacks enough evidence to close; new installed workflow check is next
Has quality tried locating that unresolved coupon and its evidence using the new page alone? The unresolved outcome can remain honest while the handling of it becomes usable.