You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suspect too in my simple example (link above) I may be using the API wrong, but I based it off the HelloWorld example found here.
The text was updated successfully, but these errors were encountered:
mamift
changed the title
Why does the WorkflowCompleted event never get published by SingleNodeEventHub (simple example included)
WorkflowCompleted event never get published by SingleNodeEventHub (simple example included)
May 28, 2021
My impression is that it would be better to re-factor DetermineNextExecutionTime and move notification out of it. I will experiment with this later. Now I think we need just a quick fix in production.
Describe the bug
The
WorkflowCompleted
event never gets published when a workflow completes.To Reproduce
See this GitHub repo: https://github.com/mamift/WorkflowCoreTests
Expected behavior
The
WorkflowCompleted
should get published by the SingleNodeEventHub when the workflow completes.Additional context
I was playing around with this gist to asynchronously await workflow completion, but it never worked for me; hanging as if deadlocked, but now I realised it wasn't because of the aforementioned gist code, it's because
WorkflowCompleted
never got published. For instance at this [line],(https://github.com/mamift/WorkflowCoreTests/blob/e75cac0aa2b092725ee2ce5ae8eabac3f2051ef7/SimpleWfTest/Program.cs#L31), it simply never triggers.I suspect too in my simple example (link above) I may be using the API wrong, but I based it off the HelloWorld example found here.
The text was updated successfully, but these errors were encountered: