Data Action 502 Bad Gateway on ServiceNow Integration

What is the standard approach to handle 502 Bad Gateway errors when the Genesys Cloud Data Action invokes our ServiceNow REST endpoint via the EU-West-1 region? The payload contains standard conversation context fields, yet the integration consistently fails after three retries despite valid OAuth tokens and correct endpoint configuration. Need to know if this is a timeout issue or a serialization mismatch in the webhook payload structure.