[Cross-post from old blog.]
Here's a great blog post at Matt Meleski's blog regarding failed message routing and failed orchestration routing within BizTalk Server 2006.
Some great screenshots and examples included.
Also, from MSDN:
When failed message routing is enabled, BizTalk Server does not suspend the message—it routes the message instead. Failed message routing can be enabled on both receive and send ports, with the following results:
- If failed message routing is enabled on a receive port and a message fails in the receive pipeline or in routing, a failed message is generated. In the case where an error occurs in or before the disassembly phase, the error message is a clone of the original interchange.
- If failed message routing is enabled on a send port and the message fails in the send pipeline, a failed message is generated.
When a failed message is generated, BizTalk Server promotes error-report-related message context properties and demotes regular message context properties before publishing the failed message. Compare this to the default behavior when failed message routing is not enabled: Messages that fail are suspended.