batch trigger external trace propagation

Author: ericallam

apps/webapp/app/routes/api.v2.tasks.batch.ts

@@ -103,10 +103,9 @@ const { action, loader } = createActionApiRoute(
       return cachedResponse;
     }
 
-    const traceContext =
-      traceparent && isFromWorker // If the request is from a worker, we should pass the trace context
-        ? { traceparent, tracestate }
-        : undefined;
+    const traceContext = isFromWorker
+      ? { traceparent, tracestate }
+      : { external: { traceparent, tracestate } };
 
     const service = new RunEngineBatchTriggerService(batchProcessingStrategy ?? undefined);
 

apps/webapp/app/runEngine/services/batchTrigger.server.ts

@@ -42,7 +42,7 @@ export type BatchProcessingOptions = z.infer<typeof BatchProcessingOptions>;
 
 export type BatchTriggerTaskServiceOptions = {
   triggerVersion?: string;
-  traceContext?: Record<string, string | undefined>;
+  traceContext?: Record<string, string | undefined | Record<string, string | undefined>>;
   spanParentAsLink?: boolean;
   oneTimeUseToken?: string;
 };

references/d3-chat/src/app/api/demo-batch-trigger/route.ts

@@ -0,0 +1,18 @@
+import { NextResponse } from "next/server";
+import { tasks } from "@trigger.dev/sdk";
+import type { todoChat } from "@/trigger/chat";
+
+export async function POST(request: Request) {
+  const body = await request.json();
+
+  const handle = await tasks.batchTrigger<typeof todoChat>("todo-chat", [
+    {
+      payload: {
+        input: body.input,
+        userId: "123",
+      },
+    },
+  ]);
+
+  return NextResponse.json({ handle });
+}