Exception is not propagated to parent orchestration as expected about durabletask-mssql

[cgillum]

I spent some time debugging this and I think the problem is that the database schema needs to be updated to support correctly persisting detailed exception information. From what I can tell, we're only saving the exception message, which isn't something we can correctly deserialize back into code. This is definitely a missing feature.

[cgillum]

@moldovangeorge can you share the demo app that reproduces this issue?

[moldovangeorge]

Sure :

1. Clone the repo from here : https://github.com/MoldovanG/DaprWorkflowAnalysis
2. Replace YOUR_CONNECTION_STRING_HERE with a connection string to a SqlServer you have at hand
3. Modify the DtfActivity to throw exception instead of logging.
4. dotnet run
5. curl --location --request POST -k 'https://localhost:5004/api/dtfworkflow' --header 'Content-Type: application/json' --data-raw '{ "numberOfParallelSubOrchestration" : 1, "numberOfParallelActivities" : 1}'

[wros]

I have this same problem using the function, in isolated mode. The Exception is not propagated to the orchestration, and I cannot use the custom retry in the activity.

I'm using the Azure Version.

When I use the SQL Provider

Here when I don't use the SQL Provider:

Obs: I'm using the VS 2022 default template for Azure Functions.

[cgillum]

Thanks @wros for the additional context. This helps narrow things down. I haven't had a chance to look at this yet but hoping to get to it soon'ish.