When replaying, using the concurrencyLimit from the original run’s queue

triggerdotdev · Dec 12, 2024 · ebd9767 · ebd9767
1 parent 1c631a1
commit ebd9767
Showing 1 changed file with 14 additions and 3 deletions.
diff --git a/apps/webapp/app/v3/services/replayTaskRun.server.ts b/apps/webapp/app/v3/services/replayTaskRun.server.ts
@@ -78,16 +78,27 @@ export class ReplayTaskRunService extends BaseService {
         environmentId: authenticatedEnvironment.id,
       });
 
+      //get the queue from the original run, so we can use the same settings on the replay
+      const taskQueue = await this._prisma.taskQueue.findFirst({
+        where: {
+          runtimeEnvironmentId: authenticatedEnvironment.id,
+          name: existingTaskRun.queue,
+        },
+      });
+
       const triggerTaskService = new TriggerTaskService();
       return await triggerTaskService.call(
         existingTaskRun.taskIdentifier,
         authenticatedEnvironment,
         {
           payload: parsedPayload,
           options: {
-            queue: {
-              name: existingTaskRun.queue,
-            },
+            queue: taskQueue
+              ? {
+                  name: taskQueue.name,
+                  concurrencyLimit: taskQueue.concurrencyLimit ?? undefined,
+                }
+              : undefined,
             concurrencyKey: existingTaskRun.concurrencyKey ?? undefined,
             test: existingTaskRun.isTest,
             payloadType: payloadPacket.dataType,