Does anyone know why our AppFoundry integration is suddenly receiving 403 Forbidden errors when attempting to register SIP endpoints via the POST /api/v2/telephony/sip/lines endpoint, specifically during the OAuth token refresh cycle for our multi-org deployment? We are running version 2023-12 of the Genesys Cloud SDK and have observed this issue persisting for the last 48 hours across three distinct tenant environments located in the us-east-1 region. The error occurs precisely when the background service attempts to re-register agents after the access token expires, despite the refresh token being valid and successfully exchanging for a new access token via the POST /api/v2/oauth/token endpoint. The response body indicates "error": "insufficient_scope" with a message suggesting the telephony:sip:write scope is missing, yet our OAuth client configuration explicitly includes this scope along with telephony:admin and telephony:sip:read. We have verified that the application permissions in the Genesys Cloud admin console are correctly assigned to the integration user, and no recent policy changes have been enacted by the tenant administrators. Interestingly, manual registration calls using a fresh token generated via Postman succeed without issue, pointing towards a potential caching or propagation delay in the scope validation service within the Genesys Cloud platform. We are also monitoring the API rate limits and have not hit the threshold for our tier, ruling out throttling as the cause. The logs show the request headers are correctly populated with the Authorization: Bearer <token> and Content-Type: application/json fields. This behavior is disrupting our automated failover mechanisms for SIP trunks, causing intermittent registration drops that impact call routing reliability. We need to determine if this is a known platform bug related to scope propagation after token refresh or if there is a specific header requirement we are missing in our automated registration flow.