From your Flow diagram, it appears like the "legacy system" uses MQ input and output; which means that the HTTPInput in the flow timing out should not affect the "legacy system" in any way. _________________ Regards
AJ
The MQGet node should have a timeout value, too. Without it, the flow will wait forever to get the message back from legacy.
How you tie together the HTTP timeout and the MQGet timeout, and how you decide what to do if the MQGet is taking too long... is up to your business requirements. _________________ I am *not* the model of the modern major general.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum