简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
CallumCarter0969 · 2025年11月17日 21:42 UTC
Check the saved request and raw acknowledgement for an attempt identifier before adjusting timestamps; keep each source's original order and mark the restart so repeated labels don't get merged.
12分Raw acknowledgement has the same job label too. The export drops the request sequence, although the application may retain it elsewhere. I've asked the developer for that rather than shifting the clocks.
11分What does acknowledgement mean in this interface: received request or completed check? Keep that question separate from finding its owner.
10分Priya, yes, and the sequence needs an agreed meaning too, not merely a number that happens to appear in two files.
0分Priya, request received only. Developer found sequence values on the two sends but no retained sequence for this acknowledgement. So we still cannot assign the receipt reliably.
7分Then keep it unassigned in the report. Does the future export retain the missing field, if the live interface provides it?
2分That export change is under review. Thanks Sam and Priya; old receipt stays unassigned, both inspection outcomes remain unknown. Better than giving the retry a success it did not earn.
9分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .