Chris Gillum

@olitomlinson per an earlier discussion with @yaron2, I think the best path forward is to have a list of supported state stores for workflow, similar to actors (it would necessarily...

@WhitWaldo I don't believe we have an issue tracking progress of this work. However, I do have an old PR that does the foundational work in the `durabletask-go` dependency to...

@halspang thanks for the comment. The odd thing is that the behavior seems to be different depending on whether the app is completely down or just unresponsive. If the app...

FWIW, I ran into a similar issue earlier today when running a Functions container locally in Docker. I don't have the logs anymore, but one issue I noticed was that...

Looks like the work has been mostly completed and just needs to be reviewed/merged.

The MSSQL storage provider is already supported by the Durable Functions Monitor project. More information here: https://github.com/microsoft/DurableFunctionsMonitor/tree/main/custom-backends/mssql.

@mmajcica are you running this against a SQL database that has existing data? If so, is it possible that some existing data might be too large to be loaded by...

I don't expect this will be a high use-case feature, but marking it P1 for the sake of SDK consistency.

@msfussell I think you're actually comparing two separate things: the Dapr Workflow SDK (in the Java example) and the Dapr SDK APIs for workflow management (your .NET and Python examples)....

Thanks @salaboy for offering to help with this! Regarding the deprecation of generic DaprClient APIs for workflows, a decision has been made to go ahead and remove them, and some...