Stop blanket resubmission first; pending is not evidence that a request never left.
简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。
Which housing jobs can startup still submit after this crash?
NathanArcher0373 · 2026年8月20日 14:26 UTC
16 条回复
Who can reconcile a housing when the file and the receiver disagree?
9分Anna's question needs an actual person, but they also need somewhere to leave it undecided. A supervisor choosing between resend and complete is still guessing if both buttons require evidence they haven't got.
16分Automatic resend is disabled. The cell lead owns reconciliation; the existing file only has pending or done.
10分I'd make a small offline copy with a housing that has definitely never reached the send step and another stopped after that step starts. Restart both. You want to see the first eligible for normal submission and the second held for reconciliation, without needing a robot to demonstrate the difference.
22分David, a send-step flag written afterwards leaves the same crash gap. The durable record has to capture the intent before the possible external effect, and a crash there still leaves uncertainty rather than proving delivery.
13分Yes, I was too loose about the boundary. I meant a persisted intent before calling out, not a note afterwards. The test should interrupt on both sides of that write as well as around submission and result storage; otherwise it can pass while keeping the original hole.
15分Does reopening a held record preserve the hold, or quietly turn it into pending again?
8分Also test an old saved result arriving after restart. It must not complete a different attempt.
7分Found that exact reopen problem in the offline copy. Unknown states were loaded as pending by default.
8分That default needs a test of its own. Include a state the current program doesn't recognise, not just the new hold state, so an older installation cannot silently reinterpret a newer file as work to send.
11分And keep the original file format version with the record. I'm not suggesting the software magically understand a future format; refusing to offer submission is a valid response when it cannot interpret the evidence it loaded.
9分Parser now refuses unknown states. Repeated reopen preserves the uncertain housing, and the unsent example stays separate. Receiver lookup still unconfirmed.
20分Then the lead needs an unresolved list, not a promise that every held housing will be recoverable.
20分Added that list. Offline crash tests pass around intent, send and save; actual receiver correlation remains with the integrator.
10分Keep automatic retry off for those legacy pending records; the new parser cannot reconstruct their missing history.
4分