简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
LucaCarter0961 · 2026年2月18日 11:36 UTC
Can they name the two events separately and show the case where a request has been received while the area remains occupied? That ought to expose the difference faster than another argument about one word.
24分They walked that case. Machine can acknowledge receipt while the previous part is still present, so the current diagram's single ready arrow is wrong. We have separate receipt and availability entries now.
9分What does the operator see while the request is received but the area is still occupied?
21分Draft screen says request received, waiting for loading area. Author still needs to define what clears availability after use and how the same request is identified after a restart.
13分Has that clearing rule been agreed yet? The two labels help, but the next request should not inherit availability from the previous exchange merely because nobody withdrew it.
24分Agreed now, with retained request identity and explicit unknown states after interruption. Offline sequence checks passed. The operator understood the two waits in the walkthrough; installed interface verification remains open. Thanks, Harish, the occupied-area example ended the word game.
6分Can the support contact identify that request from the operator's view now?
21分