The BizTalk product team introduced the Failed Message Routing feature in version 2006. Before that there was not an out of the box ability to resume messages that could not be routed or failing for another reason. Failed messages were placed into the Message Box and suspended, and no BizTalk application could subscribe to these messages for either troubleshooting or repair actions. For BizTalk 2006 and subsequent versions, failed message routing allows you to enable routing for failed messages. It means a developer can create an orchestration process or message Send ports that subscribe to any exceptions that occur at messaging level. These exceptions at this level can occur in adapter processing, pipeline processing, mapping, or message ....