Workflow with one-way contract (only Receive), NamedPipe transport with TransferMode = Buffered – observed behavior

I came across this behavior a few days back while investigating a bug.   Here’s what I had: Workflow: 1. Has a number of activities executing in sequence. None of the activities are of type AsyncCodeActivity, and none of the activities create Bookmarks. 2. The Workflow starts off with a Receive, and has no SendReply….