If you have started a job (see “To run a selected job”) but observe that related background tasks are not executed as expected, the job may be locked. To resolve such a situation, you can unlock a job via the web service call: unlockJob
This operation manually removes the lock which protects the job against concurrent job executions.
In normal system operation, the job management will lock or unlock jobs automatically to ensure that a job is not executed twice at the same time. However, if the system is restarted (or crashes) while a long-running job is executing, such a lock may be orphaned. This orphaned lock will prevent further executions of the job.
Only in such a situation this operation should be used to manually remove the orphaned lock to continue normal operation.