So I’m seeing a very odd bug with our ServiceNow MID Server integration. The MID server successfully retrieves the initial OAuth2 token from Genesys Cloud via POST /api/v2/auth/token, but subsequent requests to GET /api/v2/conversations/details fail with a 401 Unauthorized. The access_token is clearly being passed in the Authorization header as Bearer . The token expiration in the initial response is 3600 seconds, and the failure occurs within minutes. ServiceNow logs show the exact header format. Is there a specific scope requirement for conversation details that isn’t documented, or is the MID server cache invalidating the token prematurely? We are using the latest ServiceNow Jakarta release and Genesys Cloud API v2.