title: Preventing Dehydrated instances when using Parallel Convoy Correlation and messages are missing
body: <p>I have an orchestration that gets activated by 1 of 2 types of messages coming in on a parallel shape. The messages are correlated by ID and status and then the remainder of the orchestration gets executed (and the messages get combined into 1).</p>
  
  <p><img src="https://i.stack.imgur.com/srQ7V.png" alt="enter image description here"></p>
  
  <p>I would like to devise a way to prevent dehydrated instances of the orchestrations from happening when one of the 2 messages does not come through. So basically, 1 message comes in and the other doesn't, the orchestration instance gets dehydrated while waiting for the second message.</p>
  
  <p>I've been doing a bunch of searching and found a few decent ways to do it if this was serial convoy, but it's not and the order of the messages cannot be guaranteed. </p>
  
  <p>For example, <a href="http://biztalkvillage.blogspot.ca/2012/12/sequential-convoy-using-listen-shape-in.html" rel="nofollow noreferrer">this post</a> is very helpful in terms of serial convoys, but still does not satisfy my requirements.</p>
  
  <p>I tried using a listen shape with each of the messages on its own branch and a delay on the third branch, but learned that if you are activating with a listen, all branches must activate and since the delay shape cannot activate an orchestration, it will not compile.</p>
  
  <p>Any suggestions, or should I just give up and go for making a separate database in order to correlate the messages manually using pipelines?</p>