简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
WendyBowen · 2026年2月14日 01:02 UTC
Ask whether the application retains that message and the state changes before it. We once kept recording the aftermath because nobody had checked an existing event file. The phone was not the only witness.
12分There is an event file. I can read the wait message there, but the fixture identity is only shown as a number. I have asked the author what that number selects.
15分Does support have the same fixture revision you're using, Wendy? My ticket was linked to the previous insert, so even a clear description kept getting the wrong answer.
13分And ask what ordinary confirmation ends the wait, because an acknowledgement of receipt and a completed fixture check can be two different events even when the screen calls both ready
23分Hassan, the ticket attachment is the current fixture drawing. Owen, author says it is waiting for the receiving check to complete, not just for the request to be received.
15分Keep the blurry clip anyway. You may still match the visible sequence to the event file. Just don't sharpen a guess into the official message text.
20分The exact message from the file and the author's explanation are the useful pair now. Does the file include the request before that receiving check?
15分Yes. Request followed by the wait. No completion recorded in that interval. The file does not tell me whether the receiving check ran and its response was lost.
12分That's the next question for the receiving side. Missing from one file can mean more than one thing.
21分I've sent the identified occurrence and asked for the corresponding receiving-side history. No new demonstration arranged. My original report was essentially 'look, it stopped', so this is more useful already.
16分Has the receiving-side owner acknowledged that request, Wendy, or are you still waiting for sales to find them?
16分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .