X_JOB_CLAIM_QUEUES_EMPTY
Means
a driver was asked to claim with queues: []
Typical cause
an empty list names no queue, and the two shipped drivers had two meanings for it — every queue on the memory driver, the default queue on the Postgres one — while ClaimOptions.queues documented neither. Each meaning is silently wrong in the other's deployment: one takes work this worker was never configured for, the other drains nothing and reads as an idle queue. Reachable only by an embedder, since jobWorker passes exactly one queue per pass
Fix
pass the queue by name — driver.claim({ queues: ['default'], limit, visibilityTimeoutMs, workerId }) — or read the list from jobs.queues, which is what jobWorker walks one queue at a time