In the Juniper Mist AI ecosystem, troubleshooting the mobility experience of a user requires analyzing the transitions between Access Points (APs). When a client reports a "poor experience when moving," it almost always points to a breakdown in the roaming process, such as sticky clients (devices that refuse to move to a closer AP), slow handoffs, or authentication failures during a roam. The Marvis Query Language (MQL) provides a conversational and structured way to extract this specific data using the ROAMINGOF clause.

The ROAMINGOF clause is designed to filter the massive amount of telemetry collected by Mist and focus specifically on the events surrounding a client's transition from one radio to another. When you execute a query like "Roaming of [Client Name]," Marvis returns a detailed visualization of the client's journey. This includes the signal strength (RSSI) at the time of the roam, the duration of the handoff, and whether the roam was "successful," "slow," or "failed".

By using this clause, an administrator can quickly identify if the "poor experience" is caused by poor overlap (where RSSI drops too low before a new AP is found) or if the client is holding onto a distant AP (sticky client behavior). Other clauses like STATUSOF (A) are used for general health checks, UTILIZATIONOF (C) tracks radio or site traffic levels, and RANK (D) is typically used to identify the best or worst performing entities (like "Rank APs by interference"). Only ROAMINGOF provides the temporal and spatial correlation needed to fix issues specifically related to user movement within the office environment.