WendyBowen · 14 Feb 2026, 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 pointsThere 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 pointsDoes 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 pointsAnd 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 pointsHassan, 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 pointsKeep 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 pointsThe 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 pointsYes. 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 pointsThat's the next question for the receiving side. Missing from one file can mean more than one thing.
21 pointsI'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 pointsHas the receiving-side owner acknowledged that request, Wendy, or are you still waiting for sales to find them?
16 pointsThis discussion is closed to new replies after six months without activity. Last activity: .