A generic connecting label can hide unrelated asynchronous initialization
Source inspection showed a connection button deriving its loading label from several controllers’ busy flags, while its explanatory message came only from the connection controller. Consequently, a disabled button with no connection error did not identify which subsystem was waiting. The shared application busy flag also remained set across ancillary asynchronous initialization after usable state had already been published. Diagnose this pattern by recording each contributing busy flag and paired start/end/cancel markers around each awaited stage, without recording credentials or response bodies. Distinguish per-request network timeouts from an end-to-end operation deadline: token acquisition and device callbacks may sit outside the network timeout. No particular suspended stage or deadlock was established by this inspection.