# Job execution beyond service bus queue 'peek lock duration'

**URL:** <https://discuss.hangfire.io/t/job-execution-beyond-service-bus-queue-peek-lock-duration/3461>\
**Category:** question\
**Created:** [June 21, 2017, 7:25pm UTC](https://discuss.hangfire.io/t/job-execution-beyond-service-bus-queue-peek-lock-duration/3461 "2017-06-21T19:25:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisjoson](https://dub1.discourse-cdn.com/flex017/user_avatar/discuss.hangfire.io/chrisjoson/32/1233_2.png) [@chrisjoson](https://discuss.hangfire.io/u/chrisjoson)\
**Post date:** [June 21, 2017, 7:25pm UTC](https://discuss.hangfire.io/t/job-execution-beyond-service-bus-queue-peek-lock-duration/3461/1 "2017-06-21T19:25:16Z")

</div>

What happens when a job executes longer than the defined Azure Service Bus Queue LockDuration in a multi-server environment? Is there a possibility that another worker might pick-up & start the same job in parallel while the first worker is still running?

Thanks