v4: batches can only complete when all their runs have been created

Author: ericallam

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

@@ -576,6 +576,13 @@ export class RunEngineBatchTriggerService extends WithRunEngine {
 
     //triggered all the runs
     if (updatedBatch.processingJobsCount >= updatedBatch.runCount) {
+      logger.debug("[RunEngineBatchTrigger][processBatchTaskRun] All runs created", {
+        batchId: batch.friendlyId,
+        processingJobsCount: updatedBatch.processingJobsCount,
+        runCount: updatedBatch.runCount,
+        workingIndex,
+      });
+
       //if all the runs were idempotent, it's possible the batch is already completed
       await this._engine.tryCompleteBatch({ batchId: batch.id });
     }

internal-packages/run-engine/src/engine/systems/batchSystem.ts

@@ -42,6 +42,8 @@ export class BatchSystem {
         select: {
           status: true,
           runtimeEnvironmentId: true,
+          processingJobsCount: true,
+          runCount: true,
         },
         where: {
           id: batchId,
@@ -58,6 +60,15 @@ export class BatchSystem {
         return;
       }
 
+      if (batch.processingJobsCount < batch.runCount) {
+        this.$.logger.debug("#tryCompleteBatch: Not all runs are created yet", {
+          batchId,
+          processingJobsCount: batch.processingJobsCount,
+          runCount: batch.runCount,
+        });
+        return;
+      }
+
       const runs = await this.$.prisma.taskRun.findMany({
         select: {
           id: true,