Durable Task: Activity Exception thrown as an unhandled exception about durabletask-dotnet

[jviau]

@GOB-Sinzinger not sure I understand your request. The sample code you shared is indeed an unhandled exception. You throw an exception from your activity, durable captures that and rethrows it in your orchestration. You catch it, but then re-throw via the throw keyword.

This is the definition of unhandled - your code is letting the exception escape.

[GOB-Sinzinger]

@jviau Thanks for your answer.

You're right, I just re-throw the exception in my orchestrator, but how else can I catch the exception and pass it to the user's output?

As far as I know, the orchestrator is the highest level, I could handle exceptions in a durable function.

I've tested with a middleware to handle the exception, but it doesn't show the expected behavior either.

My goal is to get a clean exception message in the output token of the status query.

So it looks something like this:

"name": "Function1",
"runtimeStatus": "Failed",
"output": "[Actually exception message of the activity]"

The current behavior is this output:
"output": "One or more errors occurred. (Task 'ExceptionTest' (#0) failed with an unhandled exception: Test Exception)"

[jviau]

Ah okay. Yeah the framework is dropping inner-exception details, which is what you want. This is a duplicate of #140 then.