Conditions for Releasing Job Scheme Locks set from Workbook

A job scheme lock applied from workbook is released when either:

• The workbook is closed
• The job lock is released automatically by the system *
• The user logs out
• The user logs in or changes credentials to the same laboratory in which the job scheme lock was created, or

* A job lock is released automatically by the system when the time denoted by the JOB_LOCK_RELEASE_INTERVAL_MINUTES application preference has elapsed, counted from the last time any of the following events occurred:

• The workbook was terminated but the screen not closed.
• A heartbeat was sent from the workbook client to the server to refresh the workbook locks by sending an "ExtendLockMessage" to the server to prevent the locks from expiring naturally after the release interval elapses. The frequency of heartbeat is driven by the WORKBOOK_LOCK_REFRESH_INTERVAL application preference. By default, this should be every minute.
• The workbook was submitted or refreshed. Note that, to prevent a deadlock situation in the case where a workbook update takes longer than a minute to finish, and an "ExtendLockMessage" is received whilst the workbook update is still in progress, then the "ExtendLockMessage" is prevented from taking effect whilst a workbook update is in progress.

Note: Cells may still be locked due to a formula, workflow status, or expiry date cell lock.

When a CCCLEANER batch job is run on the system batch queue (refer to Maintaining Schedules and Batch Job Executions), then job and job scheme locks with a populated LOCK_DATE time-stamp > 28 days are deleted from the CCLOCK table.