Daniel Gerlag

hmmm... looks like the appveyor pipeline is still passing even though tests are failing... will need to check that

Did you start the workflow host?

Could you include a project that replicates this issue? The workflow data serialization for MongoDB does work in the examples.

Currently, the parameter for the prompt does not take an expression... that is something we'd have to add.

Not sure this is something the workflow engine should take responsibility for, have you considered implementing idempotency checks in the calling process?

You could store the workflow instance ID and your reference in your own storage and check against that?

> Would that not be a two phase commit? That depends on how you implement it... there are many solutions to this problem. That being said, it might be useful...

What is the `reverse state translation status`? Events are facts of history, they do not have a state. Workflows can respond to these facts of history, but this process is...

@Loupi ^

We could look into creating some kind of scheduled termination, where the workflow will terminate at the end of the current execution cycle if it is locked. In the meantime,...