NoraAllen0322 · 20 Jan 2026, 03:46 UTC
Split never submitted from possibly submitted first, and hold the uncertain case for reconciliation instead of allowing that startup resend.
11 pointsAutomatic resubmission is disabled while we sort it out; the developer can reproduce a crash after sending but before saving the reply, and that row now reopens as uncertain.
10 pointsWhat evidence resolves the uncertainty? A new label does not decide whether the original housing verification completed.
16 pointsCan the operator see the housing and attempt identifiers on that uncertain row? Our caller once had a good description of a wait and no way to identify which job needed help.
-8 pointsNaomi, the proposal uses the retained result tied to the original attempt plus an authorised review when that cannot settle it; Daniel, those identifiers are on the revised screen, not just hidden in the log.
20 pointsWhat happens if no matching result can be found?
10 pointsKeep it uncertain, Jo, unless their agreed review establishes an outcome; absence of a reply isn't a new permission to send.
11 pointsTest the review decision through a second restart. The row must not fall back into the old pending queue after someone has resolved it.
4 pointsThe offline cases now cover matching retained result, no result, and reopening after a saved review decision; no-result remains held and none silently resubmit. Our operator walkthrough found the call contact unclear, so that part still needs finishing.
16 pointsHave the actual contact receive the example call once named. It is an easy way to discover which identifier they need before your first real recovery call arrives.
8 pointsThis discussion is closed to new replies after six months without activity. Last activity: .