TimeoutException in WF 4.5 with content-based correlation and non-sequential operations - by wbradney

Status : 


Sign in
to vote
ID 788815 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 5/28/2013 5:12:09 PM
Access Restriction Public


With a simple, sequential workflow, correlated on an argument to the method (ie content-based correlation), with OperationA (CanCreateInstance = true, CorrelatesOn=argument) and OperationB (CanCreateInstance = false, CorrelatesOn=argument), a second client call to OperationA causes "operation is not available at this time" (as expected).
When OperationB is moved into a more complex activity (eg Pick or StateMachine), a second call to OperationA causes a TimeoutException.

When the correlation settings are moved to the CorrelationInitializer (which I suspect is the recommended approach), the workflow fails even more spectacularly, rendering the correlated workflow unusable and requiring the instance to be manually removed from the persistence store.

A comprehensive sample project is attached. I'd be glad to discuss it further with someone on the WF team.
Sign in to post a comment.
Posted by Microsoft on 6/20/2013 at 3:15 PM
Thank you for passing along this issue to us. We evaluate all the feedback our customers submit, but unfortunately we cannot fix every item that comes in. We have evaluated the issue you submitted, and at this point, we do not anticipate releasing an update for it. If the issue is blocking you from using the product, please contact our support via the Visual Studio Help and Support (http://msdn.microsoft.com/en-us/vstudio/cc136615.aspx) page on MSDN.
Posted by wbradney on 6/3/2013 at 3:57 PM
Note that these tests seem to operate identically regardless of whether SQL persistence is enabled or completely disabled. Not sure if that helps to diagnose, but it indicates to me that the issue (if there is one) is with the implantation of content-based correlation in the workflow engine rather than how they are being persisted.
Posted by wbradney on 5/29/2013 at 5:30 AM
See more discussion on the forums here:

Posted by Microsoft on 5/28/2013 at 11:19 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 5/28/2013 at 5:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)