Need some help troubleshooting an issue where the CXone API endpoint GET /api/v2/agents/states returns an empty array for agents who are clearly logged in and active in the PureCloud interface. We are building an Angular enterprise desktop wrapper using the GC Premium App framework, and we have a service layer that polls this endpoint every 15 seconds to synchronize local agent status with the cloud state. The authentication is handled via the standard OAuth2 client credentials flow, and we have verified that the access token has the necessary scopes: agent:view, agent:login. The HTTP request is structured as follows: GET https://{subdomain}.mypurecloud.com/api/v2/agents/states with headers Authorization: Bearer {token} and Content-Type: application/json. The response status code is consistently 200 OK, but the body is strictly regardless of whether the agent is in Available, Busy, or Wrap-Up state. I have confirmed the agent ID is correct by cross-referencing with GET /api/v2/users/{userId}, which returns the expected user object with status active. I have also tried appending ?expand=login to the query string, but the result remains an empty array. This behavior started occurring after a recent platform update, although our internal logs do not show any breaking changes in the API documentation. We are using the JavaScript SDK v2.45.0, and the underlying fetch call is made via the platformClient.auth.getAccessToken() followed by a direct REST call using the native fetch API. Is there a known issue with the states endpoint returning empty results for agents logged in via specific client types, or is there a required query parameter I am missing? I have also checked the NICE CXone developer community forums and the Genesys Cloud documentation, but I have not found any similar reports. The issue is reproducible across multiple agents in our Chicago-based BPO environment. Any insights into why the API would return 200 OK with an empty array instead of the expected state objects would be greatly appreciated. We need this data to drive the UI state in our Angular components, and the current behavior is causing the agent desktop to display incorrect availability indicators.