Hello Joe;
Run the web service request in a background thread and then check the
state of it using additional web services methods. Once it has
completed, add a final web service to obtain the results. Of course
polling is really inefficient so you may like to look at using a queue-
and-
What's a good way to handle a WO request, from a third party API call
(web service), that generates a long response?
For example, a web service call comes into a WO app whose response
takes 60 seconds (i.e. a large database fetch and data aggregation).
Normally, a WO long response page