views:

3

answers:

0

I'm running a State Machine workflow in Windows Workflow foundation. In this workflow, I have a state initialization task that takes a little bit to execute. In the meantime, I have an event that can fire while the StateInitialization activity is running. I think this is causing the classic "Queue: {0} is not enabled" issue that appears when the exception isn't handled properly. Any ideas?