Issue:

Currently while deploying any new BizTalk or dependent Components release,
we cleanup all the messages in the suspended queue, including suspended
messages and dehydrated messages. This cannot be allowed in a live
environment. This is because there will be certain messages in the BizTalk
suspended queue which are suspended (due to some errors) and require
attention or dehydrated if they are long running transactions due to the
presence of the Delay shape in some orchestrations.

Questions:
1. For suspended messages, we just need a copy of the suspended messages,
which can be referred to later. Can suspended messages be selectively
archived? Is there any other approach?

2. More importantly, how do we do a new release, and also ensure that the
current dehydrated messages get processed normally after the delay period?
Let us take an example to add more detail to the question. We have 3
orchestrations A, B and C in orchestrations.dll version 1.0.0.0 with A and B
being long running ones. We need to create a fresh orchestrations.dll versio
n
to be now deployed while there are some dehydrated messages of A and of B.
How do we do the new release while ensuring proper processing of the
dehydrated messages of A and B after the release?

[ Post a follow-up to this message ]