Calling GET /api/v2/agents/states with a valid access token yields an empty array [] even though the target agent is actively logged in and handling calls. The agent ID in the query string matches the one used in other successful API calls, but the response lacks the expected state object. Has anyone seen this behavior with specific agent profiles or division configurations?