ServiceNow MID Server 403 on Genesys Cloud PII Redaction API

Could use a hand troubleshooting this 403 Forbidden response when the ServiceNow MID Server attempts to call the Genesys Cloud PII redaction endpoint via the Data Action connector. The integration worked perfectly last week during the compliance audit phase.

The MID Server logs show a successful OAuth token exchange, but the subsequent POST to /api/v2/conversations/pii/redactions fails immediately. The request payload matches the schema defined in the Genesys Cloud documentation for digital channel transcripts.

Checking the Genesys Cloud audit logs reveals no corresponding request entries, suggesting the call is being dropped at the API gateway level. Has the scope for the service account used by the MID Server been restricted recently?