Error propagation is not working properly even after upgrading to latest version of Sql server

[aaditya8]

We have updated SQLServer and Core libraries for Error propagation fix and started testing with both the modes "ErrorPropagationMode.SerializeExceptions", "ErrorPropagationMode.UseFailureDetails". Please find my observations help me with my use case.

Use Case :

We have one parent orchestration , one sub orchestration under parent orchestration , one task(Activity) under sub orchestration.
I am expecting to propagate the exception occurred in sub orchestration task to both Sub orchestration and Parent orchestration. Below are my findings.

TaskHubWorker:

   var taskHub = new TaskHubWorker(orchestrationService);
   taskHub.ErrorPropagationMode = ErrorPropagationMode.UseFailureDetails;
   orchestrationService.CreateIfNotExistsAsync().Wait();

Scenarios :

With SerializeExceptions : Inner Exception is always null in Sub Orchestration and Parent Orchestration.
With UseFailureDetails : I am able to see the Failure details(Including stack trace) of the Sub Orchestration Activity in Sub Orchestration. Same way i am able to see the failure details of Sub Orchestration in Parent Orchestration but not able to see the Failure details of Sub orchestration activity. Its coming as null.

Could you please help me with this.

[cgillum]

ErrorPropagationMode.SerializeExceptions is lower priority for us since it's considered the "old" way to propagating exception information and is already quite brittle. I can't guarantee much here.

ErrorPropagationMode.UseFailureDetails is expected to work, but it looks like we don't have an integration test to confirm whether it's working for sub-orchestration + activity scenarios. I'll look into adding one and fixing any issues it uncovers.