It looks like you are using the XML Receive/Send pipelines. These pipelines have the property “Allow unrecognized messages”, which is false by default. If you were to set this property to true, then BizTalk would receive your messages, and you could use failed message routing. When you enable failed message routing on a receive port, BizTalk will attach some specal context properties to the message when an exception occurs. Then you could create another process, an SMTP send port for example, to filter on these failed messages and deliver them to someone who cares. Example filter: ErrorReport.FailureCode Exists. Keep in mind that failed message routing only works messaging exceptions, not orchestration exceptions.
Search this Site:
Recent Posts
- Logic App Consumption deployment: The secret of KeyVault parameter cannot be retrieved. Http status code: ‘Forbidden’. Error message: ‘Access denied to first party service
- BizTalk Server Visual Studio project: attempted re-targeting of the project has been canceled.
- BizTalk Oracle Adapter error: The assembly required for type mapping not found.
- PowerShell script to identify all SQL V1 actions and triggers inside Logic Apps Consumption
- Friday (funny) Fact: There is no size limit for the Logic App parameter name