Closed borsi closed 7 years ago
Workflow Start Create a ATask Parallel : WaitOnContentChanged(ATask) | Delay(10min) Delay happens. Workflow starts up again Creates new BTask WaitOnContentChanged(BTask) BTask Save -> Error
So my reasoning is that it goes wrong in the wakeup workflow after delay it's probably running with wrong workflowpath there.
after Delay Wakeup new Task then WaitOnContentChanged for the new Task = Error
...which results in wakeup errors on NotifyContextChanged
This time to do with the wake up workflows to continue for when a Task changes that you are looking at with "WaitForContentChanged" workflowaction...
The problem is in the CreateBookmark I think, somehow the context in Execute (line 32 of WaitForContentChanged.cs) has the wrong WorkflowInstancePath (ContentWorkflowExtension) from another Running workflow, maybe .
Therefor the bookmark it creates is wrong cause it points to a a different workflow.
And so on NotifyContextChanged (at Save of Task) it can't load the workflowapp and continue
—
Which you can see from below select where I join the workflownotifications table with the instancestable.
SELECT TOP 1000 w.NotificationId ,w.NodeId ,w.WorkflowInstanceId ,w.WorkflowNodePath ,w.BookmarkName, n.BlockingBookmarks FROM [SenseNetContentRepository].[dbo].[WorkflowNotification] as w INNER JOIN [SenseNetContentRepository].[System.Activities.DurableInstancing].[InstancesTable] as n ON w.WorkflowInstanceId = n.Id where BookmarkName <> SUBSTRING(BlockingBookmarks,2,36)
Following Select gives me the results in the attachment. As you will see bookmark names aren't matching.
How this happens I have no clue... Somehow the Workflow must be running with bad WorkflowInstancePath when you execute WaitForContentChanged