improvement(knowledge): log Trigger.dev batchIds for audit trail

tasks.batchTrigger returns a batchId per call. Collecting and logging
them after dispatch makes it possible to look up or cancel batches in
the Trigger.dev dashboard when investigating stuck or missing documents.

Author: waleedlatif1

apps/sim/lib/knowledge/documents/service.ts

@@ -359,10 +359,11 @@ async function dispatchViaBatchTrigger(
   requestId: string
 ): Promise<number> {
   let dispatched = 0
+  const batchIds: string[] = []
   for (let i = 0; i < jobPayloads.length; i += TRIGGER_BATCH_SIZE) {
     const chunk = jobPayloads.slice(i, i + TRIGGER_BATCH_SIZE)
     try {
-      await tasks.batchTrigger<typeof processDocumentTask>(
+      const result = await tasks.batchTrigger<typeof processDocumentTask>(
         'knowledge-process-document',
         chunk.map((payload) => ({
           payload,
@@ -381,13 +382,17 @@ async function dispatchViaBatchTrigger(
           },
         }))
       )
+      batchIds.push(result.batchId)
       dispatched += chunk.length
     } catch (error) {
       logger.error(`[${requestId}] Failed to batchTrigger ${chunk.length} document jobs`, {
         error: getErrorMessage(error),
       })
     }
   }
+  if (batchIds.length > 0) {
+    logger.info(`[${requestId}] Trigger.dev batches dispatched`, { batchIds })
+  }
   return dispatched
 }