Re: Terminate orchestration execution after a fixed amount of time

I would have thought those were the right things to use.  In the past
I've had to use a loop with listen and delay so that I could actually
keep processing and not block.  I think it's because once you've done
a send with a request response ****t you're waiting on the response.
Then I made the loop run in iterations that met my time requirements
(like 3 times for x seconds each).  Maybe you can do similar and send
before the listen / loop and have the response receive in the listen /
delay loop.  Just some thoughts.

Kind Regards,
-Dan