fetchAndLock, long polling & unlocked tasks

Camunda 7 Topics Discussion & Questions
1

FetchAndLock is still waiting for a task even the task was unlocked by the timeout earlier than asyncResponseTimeout would be over
How to reproduce

  1. Deploy any simple process with an external task
  2. Create a new process instance. It causes a new task
  3. Use Postman to call fetchAndLock. You’ll get a new task immediately
    {
    “workerId”:“aWorkerId”,
    “maxTasks”:10,
    “asyncResponseTimeout”: 30000,
    “topics”:
    [{“topicName”: “salesFlow_Mobile_TextAnswers”,
    “lockDuration”: 10000,
    “deserializeValues”: true
    }]
    }
  4. Make the call again.

Expectation:the second call of fetchAndLock will wait for 10sec then returns the same task
Actually: the second call of fetchAndLock waits for 30sec then returns the same task