403 Forbidden: Invalid Signature
Configuring the new Data Action to push compliance logs to ServiceNow via the MID Server. The Genesys Cloud webhook signature validation fails despite matching the shared secret in the X-Genesys-Signature header. Using London-based Genesys Cloud instance (2024.06.0) and ServiceNow Washington DC. The payload arrives but gets rejected before processing. Is there a specific timestamp tolerance setting in the Architect flow or ServiceNow webhook definition that needs adjustment for cross-region latency?