Is the default name intended inside Worker processor

[arthurvanl]

I thought the name was going to be the first param. But it seems that is the schedulerId

is it intended not to return the name?

For now I resolved the issue by adding the name as data into the upsertJobScheduler like this:

[egeominotti]

Good catch! This was a bug — fixed in effd637.

What was happening

When upsertJobScheduler registered a cron job, it only stored jobTemplate.data without embedding the name. When the cron fired and pushed a job, the worker extracted name from job.data.name, found nothing, and fell back to 'default'.

This is different from Queue.add(name, data), which correctly embeds the name into the data as { name, ...data }.

The fix

Now upsertJobScheduler embeds jobTemplate.name into the cron job data, matching Queue.add() behavior:

// Before (broken): name was lost
data: jobTemplate?.data ?? {}

// After (fixed): name is embedded in data
data: jobTemplate?.name
  ? { name: jobTemplate.name, ...(jobTemplate.data ?? {}) }
  : (jobTemplate?.data ?? {})

So now this works as expected:

await queue.upsertJobScheduler('my-scheduler', {
  every: 60000,
}, {
  name: 'send-email',  // ← will now appear as job.name in the worker
  data: { to: 'user@test.com' },
});

const worker = new Worker('my-queue', async (job) => {
  console.log(job.name); // 'send-email' (was 'default' before the fix)
}, { embedded: true });

You no longer need the workaround of putting the name in data manually. Update to the latest version to get the fix.

Thanks for reporting @arthurvanl!