Stuck on a persistent authentication failure when triggering a ServiceNow incident via a Genesys Cloud Architect Data Action. The integration was stable for six months but began failing after the last platform update. The endpoint is our ServiceNow MID Server, configured with basic auth headers in the Data Action settings.
The GC logs show a 401 Unauthorized response immediately after the request is sent. Network traces from the MID Server confirm no incoming request, suggesting the issue originates within the Genesys egress layer. We have verified the credentials are correct by testing the same endpoint with Postman from our internal network. The payload structure remains unchanged, containing standard JSON fields for short_description and assignment_group.
We are running the latest Architect version. The Data Action is configured as a webhook with application/json content type. No proxy changes have been made on our side. The error occurs consistently across multiple test cases, ruling out transient network issues. Is there a known issue with Data Action credential handling in recent Genesys Cloud releases, or should we regenerate the API tokens on the ServiceNow side?