Fix: BullMQ-Job-IDs ohne Doppelpunkt

BullMQ lehnt benutzerdefinierte Job-IDs mit ':' ab; dispatchJob fiel dadurch
mit Redis immer auf die Inline-Verarbeitung zurück (gemeldet von L4).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
2026-09-14 12:35:24 +02:00
co-authored by Claude Opus 5
parent e0f5e13e1c
commit da2afb79e3
+2 -1
View File
@@ -75,7 +75,8 @@ function queue(name: JobQueueName): Queue<JobPayload> | null {
export async function enqueueJob(name: JobQueueName, payload: JobPayload): Promise<boolean> { export async function enqueueJob(name: JobQueueName, payload: JobPayload): Promise<boolean> {
const q = queue(name); const q = queue(name);
if (!q) return false; if (!q) return false;
await q.add(name, payload, { jobId: `${name}:${payload.tenantId}:${payload.entityId}:${Date.now()}` }); // BullMQ rejects custom job ids containing ":" (reserved for its Redis key layout).
await q.add(name, payload, { jobId: `${name}__${payload.tenantId}__${payload.entityId}__${Date.now()}` });
return true; return true;
} }