WF 3/3.5: Event "{1}" on interface type "{0}" for instance id "{2}" cannot be delivered

  You may implement a state machine workflow and deploy it to a production server. Intermittently you may find that the workflow does not work as expected. If you enable workflow logging following the instructions in KB972914, you will see System.Workflow.Activities.EventDeliveryFailedException in the trace log:   Event “YourEventName” on interface type “YourInternfaceType” for instance id…

0

WF3/3.5: Is “ManualWorkflowSchedulerService: CanRun is False” normal in WF logging?

  A customer enabled workflow logging following the instructions in KB972914. He asked what “ManualWorkflowSchedulerService: CanRun is False” meant in WF logging. And is it normal?   As you know, if we use ManualWorkflowSchedulerService, we need to call RunWorkflow method manually. Let us check the pseudo code of this method:          public bool RunWorkflow(Guid workflowInstanceId)       {…

0

WF 4/4.5: How to emit tracking information of a child workflow

The child workflow is composed from some existing activities. This child workflow is treated as an activity in the master workflow. Sometimes we may need to track the internal activity execution information of the child workflow. However even if ActivityStateQuery.ActivityName is set to “*”, the tracking information is only from the master workflow. To get…

0

How to completely release WorkflowRuntime resource

In case you need to create multiple WF 3.5/3.0 WorkflowRuntime objects, you may find the memory usage of the workflow application keep rising (memory leak) although you have disposed the objects.   To completely release the resource of WorkflowRuntime, we need to call StopRuntime method before it is disposed. For example:                 using…

0