BAM Tracking not working correctly with custom pipeline component when message type is unknown

We recently received a problem reported by our customer that BAM tracking doesn’t work correctly with custom pipeline component when message type is unknown. Below are the details.   The problem:   We are using Microsoft Biztalk Server 2013 R2. The problem that I am having is to do with BAM. BAM isn’t “continuing” correctly…

1