You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Consider removing locks on ACM start up... but I am not sure how would it work on multi pod environment.
Also, giving a little bit of context: in my situation the locks were randomly being persisted because of AEM Author recycle activity that happens daily at various times (we identified two windows so far: 03-04 UTC and 06-08 UTC. Often in those time periods, script execution is being interrupted and the lock stays forever.
In multi pod env it is pretty hard to differentiate boot vs pod replacement. That's why locks rather cannot be removed during boot. If you could tell me how to detect boot in aemaacs I happy to do it.
Thanks for the context. I am going to dig more into that direction.
Activity
krystian-panek-vmltech commentedon Jun 26, 2026
also expire lock with configurable duration (e.g 24h by default) would be nice;
thanks for sharing it, will do within weeks
jakub-przybytek-wttech commentedon Jul 14, 2026
Consider removing locks on ACM start up... but I am not sure how would it work on multi pod environment.
Also, giving a little bit of context: in my situation the locks were randomly being persisted because of AEM Author recycle activity that happens daily at various times (we identified two windows so far: 03-04 UTC and 06-08 UTC. Often in those time periods, script execution is being interrupted and the lock stays forever.
krystian-panek-vmltech commentedon Jul 14, 2026
In multi pod env it is pretty hard to differentiate boot vs pod replacement. That's why locks rather cannot be removed during boot. If you could tell me how to detect boot in aemaacs I happy to do it.
Thanks for the context. I am going to dig more into that direction.