Microsoft KB Archive/926497
Article ID: 926497
Article Last Modified on 11/24/2006
- Windows Workflow Foundation
When using a Conditioned Activity Group (CAG) in a parallel activity, the Workflow may appear to hang and the CAG Activity never completes.
This problem occurs because the CAG incorrectly checks the status of all activities.
When you use the CAG in a parallel activity, there may be some active activities in other branches. When the CAG receives a cancellation event, the CAG checks all the children that include active activities in other branches. However, the cancellation messages for the active activities in the other branches will never come. Under these circumstances, the CAG may not respond.
To work around this problem, do not use a CAG in a parallel activity.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Keywords: kbtshoot kbprb KB926497