Job activation resolves before all jobs are retrieved

[huygur]

SDK Component

activateJobs() method is not working as expected (as it is documented in the original Zeebe API).

Expected Behavior / Current Behavior

If Zeebe activates 20 jobs, I would like to access all 20 jobs.

• When I try to activate a job that doesn't exist (ex: invalid type)
  • Expected behavior: If I pass 5000 to requestTimeout, method should respond with 0 jobs after 5 seconds
    Current behavior: If I pass 5000 to requestTimeout, method does not respond / is stuck
  • Expected behavior: If I pass -1 to requestTimeout, method should respond with 0 jobs immediately
    Current behavior: If I pass -1 to requestTimeout, method does not respond / is stuck
• If I have 20 process instances running on the same process, on the same flow node (a service task), and I try to activate jobs with the following parameters:

{
    "maxJobsToActivate": 20,
    "requestTimeout": 5000,
    "timeout": 1000,
    "type": "some-type",
    "worker": "some-worker"
}

Expected behavior: Zeebe activates 20 jobs, I get 20 jobs
Current behavior: Zeebe activates 20 jobs, I get 6 jobs

Possible Solution

Currently stream is waiting for the data and resolves immediately once some data is available:

camunda-8-js-sdk/src/zeebe/zb/ZeebeGrpcClient.ts

Line 291 in dd5717e

resolve(jobs)

Also, there is no stream.end function which makes the method stuck until there is some data.

Here is a PR: #213

Steps to Reproduce

Context (Environment)

[jwulf]

Thank you for identifying this, and for the PR to fix it!

[jwulf]

Release 8.6.9 contains this fix.