I’m curious as to why the Data Action configured to push conversation metadata to ServiceNow is returning a 403 Forbidden error specifically when triggered by a digital channel webhook? The integration has been stable for six months, but since the last Genesys platform update, the POST request to our ServiceNow REST API endpoint (/api/now/table/incident) is being rejected. The error response body indicates Invalid OAuth token or Scope mismatch, which is confusing because the Premium App credentials stored in the Genesys secret manager were verified and rotated last week. The webhook payload structure remains compliant with the documented schema for digital channels. I have confirmed that the ServiceNow user account associated with the OAuth client has the sn_incident_write role assigned. Is there a change in how Genesys handles token refresh for outbound Data Actions that might be causing the token to expire mid-flight? The logs show the request is leaving Genesys successfully but failing at the ServiceNow gateway. Checking the Network Trace in Genesys shows the initial handshake is fine, but the subsequent payload delivery fails. Thank you.