I know Martijn H posted on this exception a while back but I think it’s worth regurtitating. I’ve seen it a few times, a couple of times recently and a few times about a year ago. Recently the issue was because a send port wasn’t enlisted so there wasn’t a subscriber for the message sent from the orchestration. Last year, I was using direct binding and my context properties weren’t set up correctly (although a subscribing orchestration was enlisted) so the subscription...