Are Job Workers tied to specific processes?

[kartenhaus]

A job worker can subscribe to a task with a specific type. However I can deploy two different processes with service tasks having the same type.

What happens if I run a job worker requesting a type that matches two different service tasks?

service-task-1 (type: process-payment)
service-task-2 (type: process-payment)

zeebe client: job worker requesting jobs of type process-payment.

Will my job worker request jobs for both service-tasks sharing the same type?

This is a bit undesirable as we now have to make sure service task types are unique.

[GotnOGuts]

I’m willing to be corrected, but:
Are Job Workers tied to specific processes? No
What happens if I run a job worker requesting a type that matches two different service tasks? Job worker will get jobs from any/all processes where the task-type matches, and potentially multiple tasks within a single process
Will my job worker request jobs for both service-tasks sharing the same type? Yes

I think that a Job Worker will respect tenant requirements, but beyond that, if you are looking for a Job Worker, it will do so strictly based on the type.

This is intentional and is a code-reuse design. If you have a general purpose “REST POST” worker, you can send any REST post from any job to it, and it will happily take “URL”, “Headers”,“Body” as the variables, and make the call, not caring what process needed to make the REST call.

Thinking of it in manual process terms…
You want an accountant to update your financial records. The transaction has a From Account, a To Account, an amount, and a reference number. You don’t really care what process initiated the transaction, nor which accountant does the update.