Stale locks in JCR repository prevent scripts from running without a good explanation / user feedback.
When a console lock is in place at /var/acm/lock/executor an attempt to run a script ends up with "SKIPPED" message and no information why the script was skipped at all.
Only logs (even at debug level) are not helpful
25.06.2026 13:58:51.002 *DEBUG* [sling-threadpool-9d8a34b6-face-46b9-83d8-6e0d1b07123b-(apache-sling-job-thread-pool)-12-AEM Content Manager Execution Queue(dev/vml/es/acm/ExecutionQueue)] dev.vml.es.acm.core.code.ExecutionQueue Execution started 'QueuedExecution[id=2026/6/25/13/58/d6ed943e-5899-47ee-9963-f3ed5976ec42_11,userId=jakub.berlinski,executable=Code[id=console],status=ACTIVE,duration=0]'
25.06.2026 13:58:51.770 *DEBUG* [sling-threadpool-9d8a34b6-face-46b9-83d8-6e0d1b07123b-(apache-sling-job-thread-pool)-12-AEM Content Manager Execution Queue(dev/vml/es/acm/ExecutionQueue)] dev.vml.es.acm.core.code.ExecutionQueue Execution skipped 'ContextualExecution[id=2026/6/25/13/58/d6ed943e-5899-47ee-9963-f3ed5976ec42_11,userId=jakub.berlinski,executable=Code[id=console],status=SKIPPED,duration=61,error=<null>]'
Please add lock information in GUI (for example in Executor panel) that would list active locks, when they were created and what script are they referencing.
Stale locks in JCR repository prevent scripts from running without a good explanation / user feedback.
When a console lock is in place at
/var/acm/lock/executoran attempt to run a script ends up with "SKIPPED" message and no information why the script was skipped at all.Only logs (even at debug level) are not helpful
Please add lock information in GUI (for example in Executor panel) that would list active locks, when they were created and what script are they referencing.