Clear Resource Reservation Lock

3 votes

We experienced an issue where a user removed the resource dependency on a daily job after it had already set a reservation lock (the resource was already in use by another job). The reservation lock was not cleared after the dependency was removed, which caused the resource to lock completely. It required clearing it from SQL.

I understand that it isn't good practice to remove the dependency from the daily job. However, it makes sense that the system should recognize the job update and remove the reservation lock. We experience similar locking issues when a job is force started to bypass its dependencies. It causes the resource to lock and often require manually clearing the lock from SQL. Again, it'd make better sense that the system recognize this bypass and clear the reservation lock on its own.

Collecting community feedback OpCon Suggested by: Hidden identity Upvoted: 22 Aug, '22 Comments: 0

Add a comment

0 / 1,000

* Your name will be publicly visible

* Your email will be visible only to moderators