What you are seeing is due to timing. When you send your message, if the server replies quickly, the second query window will open and be the active window before the away reply is received, so the away reply is displayed in the status window. If the away reply is received before the second query window opens, your current query window will be active and the away reply will be displayed there. This type of timing issue is more apparent when features that depend on the active window, and open windows themselves, are tested in the same client.