[Bug]: processBy field missing in job data despite worker name configuration

[dzmm]

Version

5.12.10

Platform

NodeJS

What happened?

When creating a new worker with a specified name, the processBy field is not being set in the job data stored in Redis. This prevents tracking which specific worker machine processed a job, making it difficult to identify and analyze problematic workers.

How to reproduce.

1. Create a new worker with a specified name:

const worker = new Worker<T, R, N>(queueName, wrappedProcessor, { 
  ...opts, 
  name: workerName,
  metrics: {
    maxDataPoints: MetricsTime.TWO_WEEKS,
  },
});

2. Process jobs using this worker
3. Inspect the job data in Redis

### Relevant log output

```shell
On job data, this is all we got.
name: Ttsv2Config
atm: 1
processedOn: 1726625871379
data: {"text":""}
priority: 0
timestamp: 1726625871371
delay: 0
ats: 1
finishedOn: 1726625881199
returnvalue: {"uploadJobId":"1938","..."}
opts: {"backoff":{"delay":100...}
pb: tts-cosy-RUNPOD-wg5...

Code of Conduct

• I agree to follow this project's Code of Conduct

[dzmm]

still have no solution for this, we can not see any worker information even from taskforce.sh

[roggervalf]

hi @dzmm processedBy is saved as pb, looks like taskforce ui is missing to show that value cc: @manast

[dzmm]

hi @dzmm processedBy is saved as pb, looks like taskforce ui is missing to show that value cc: @manast

Hi @roggervalf I don't think that is the reason, even on redis we cannot see which worker processing/processed it

[manast]

@dzmm in the code you pasted in the beginning of the issue I can see a "pb" field actually. @roggervalf is right in that this data is still not being shown in Taskforce. Prioritising this up now.