Extend the lock of a job delivered over the gRPC job stream
Changed onMoves the lock deadline of a job to now plus lockDuration (absent: the lock duration of the subscription the job was delivered under, capped by jobManager.maxLockDurationMs) and answers the new deadline. clientId is the client id of the job stream the job was delivered to; a job which is not locked at the moment (the lock lapsed, the job was completed or failed) or which is locked for a different client answers 409, and the job itself is left untouched. With deliveryToken only the lock of that delivery is extended: a lock the job holds for another delivery, as after this delivery's lock lapsed and the job came back to the same client, answers 409 too. It exists for workers which receive jobs over the stream but send their commands over REST. Jobs fetched through GET /jobs hold no lock and cannot extend one.
Request
- Base URL: http://localhost:8080/v1
- URL: http://localhost:8080/v1/jobs/{jobKey}/extend-lock
- Auth: none declared
Path parameters
Request body
Example request
{
"lockDuration": "PT5M"
}Response
Lock extended
Changes
- info
endpoint added
- info