Consider the following scenario:
You define a BAM activity and a BAM tracking profile to enable the continuation between one Receive port and one Send port in Microsoft BizTalk Server.
You use a custom pipeline that contains at least one pipeline component in the previous Receive port or in the previous Send port.
In this scenario, the continuation is unsuccessful.
This issue occurs because BAM tracking data is not recorded correctly in the related BAM Activity tables.
Cumulative update information
The fix that resolves this issue is included in Cumulative Update 2 for BizTalk Server 2013 R2.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the service pack and cumulative update list for BizTalk Server.
Learn about BizTalk Server hotfixes and cumulative update support.