Architect Data Action 502 when triggering ServiceNow from Outbound Campaign

General Discussion
1

Anyone free to help troubleshoot this 502 Bad Gateway returned by the Data Action step within an Architect flow triggered by an Outbound Campaign dialer event. The flow executes correctly in test mode but fails intermittently in production during peak hours (10:00-14:00 GMT) with a timeout on the ServiceNow REST endpoint.

  1. Outbound Campaign initiates call via standard predictive dialer.
  2. Architect flow captures the conversation.created event.
  3. Data Action step invokes ServiceNow cmdb_ci table via HTTP POST.
  4. ServiceNow returns 502 to Genesys Cloud webhook receiver.