Predictive Routing: Data Action Timeout Causing Queue Assignment Failure

Can anyone clarify why a Data Action call to ServiceNow causes a Predictive Routing queue assignment to fail with a 504 Gateway Timeout? The flow triggers a REST API call to validate customer tier before offering the queue. When the MID server latency exceeds 5 seconds, the Architect step fails, and the interaction drops to the default queue instead of the intended digital channel skill group.

The ServiceNow endpoint is stable, but GC enforces a strict timeout. Is there a way to configure async execution here so the routing decision waits for the response without dropping the interaction? We are using the latest Architect version in the Europe/London region.

The problem here is…

Data Action Timeout: 504 Gateway Timeout

WFM scheduling doesn’t handle this, but Architect does. Increase the timeout in the Data Action config to 10 seconds. Also, check if the ServiceNow endpoint is caching. This fixes the drop to default queues.