fix: don't overwrite specific error message in catch path

Address review feedback from @YunchuWang: in the catch block, setSpanError
sets the span with the actual exception message, but setOrchestrationStatusFromActions
would then overwrite it with a generic 'Orchestration failed' because the
synthesized action has undefined result.

Now the catch path sets the status attribute directly without calling
setOrchestrationStatusFromActions, preserving the specific error message.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: torosent

packages/durabletask-js/src/worker/task-hub-grpc-worker.ts

@@ -25,6 +25,7 @@ import { VersioningOptions, VersionMatchStrategy, VersionFailureStrategy } from
 import { compareVersions } from "../utils/versioning.util";
 import * as WorkerLogs from "./logs";
 import {
+  DurableTaskAttributes,
   startSpanForOrchestrationExecution,
   startSpanForTaskExecution,
   processActionsForTracing,
@@ -705,6 +706,9 @@ export class TaskHubGrpcWorker {
       // Record the failure on the tracing span
       if (tracingResult) {
         setSpanError(tracingResult.span, error);
+        // Set just the status attribute — don't call setOrchestrationStatusFromActions
+        // which would overwrite the specific error message with a generic one
+        tracingResult.span.setAttribute(DurableTaskAttributes.TASK_STATUS, "Failed");
       }
 
       const failureDetails = pbh.newFailureDetails(error);
@@ -718,11 +722,6 @@ export class TaskHubGrpcWorker {
         ),
       ];
 
-      // Set orchestration status on the span for the failure path too
-      if (tracingResult) {
-        setOrchestrationStatusFromActions(tracingResult.span, actions);
-      }
-
       res = new pb.OrchestratorResponse();
       res.setInstanceid(req.getInstanceid());
       res.setCompletiontoken(completionToken);