Our application crashed after submitting a coupon check and before saving the outcome. The local file still says pending, and startup would send it again. I have stopped using that helper. How should we distinguish never sent from sent with an unknown result before the covering shift touches this?
I cannot decide whether this pending FR10 coupon was already checked
CarlaAllen0314 · 2026年3月15日 17:17 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
12 条回复
Retain the submitted attempt and mark its outcome unknown. Have the interface owner reconcile any durable controller-side or application evidence for that identity before deciding whether another inspection is needed. Pending alone is too vague for automatic resubmission.
13分The developer has split never submitted from submitted without a known outcome. We retained the original attempt identity. They found a saved receipt for it, but no result yet.
8分Receipt tells you it was received. Do not promote it to a completed check.
11分Can the person on shift identify the physical coupon that goes with that attempt, Carla? The software distinction helps, but it will not identify a loose sample by itself.
15分回复 OmarBell0665
The coupon is labelled and retained separately. Its identity matches the attempt. Quality has not accepted it from the receipt, and the developer has made the missing-result reason visible.
18分Much better than a button labelled try again.
12分Test startup with one definitely unsent record and one submitted-unknown record. Also reopen after a reviewed decision is saved, so the second startup does not recreate the uncertainty.
3分Those tests pass offline. Submitted-unknown stays held, and the recorded decision survives reopening. The original coupon is still awaiting its separate review because the result was not recovered.
6分So the helper is improved. The coupon outcome is not reconstructed.
19分Has the covering shift tried the new wording without the developer explaining it? I would like to hear whether unknown sounds different from rejected to them.
22分回复 OmarBell0665
They understood unknown but thought the review button would run another check. We are changing that wording with the trainer. The revised helper is not back in use yet.
7分Useful find. Keep the button's actual action explicit and repeat that walkthrough before issuing it.
19分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .