Daniel Gerlag

No code has changed from our side, only the version of EF... perhaps the new version has a different default transaction isolation level or something. I will do some digging.

I have released a new version with the latest EF core and removed MARS. I have no been able to reproduce the issue, but please test with the latest version...

So, the WorkflowRepository is meant to be an internal concern of the library... but if you elect to use it in your own code, I would advise you to also...

EFCore dropped support for netstandard2.0 in v5

https://github.com/danielgerlag/workflow-core/pull/936

you can pass object graphs to step inputs as opposed to just scalar values ``` "inputs": { "Body": { "Value1": 1, "Value2": 2 }, "Headers": { "Content-Type": "application/json" } },...

Going to be travelling for a few weeks but I'll try take a deeper look soon.

@kirsanium I haven't forgotten about this PR. I will try carve out some time in the next week or so to dive deeper into it but on the surface it...

If we used the [TransactionScope](https://docs.microsoft.com/en-us/dotnet/api/system.transactions.transactionscope) API, we wouldn't have to change the persistence provider interface.

Looks like some integration tests are failing