Thanks for opening this issue. Originally, we were doing auto-recovery of "locked" tasks running beyond a set timeout (Scheduler config > Task Timeout). With the conversation from joomla-projects/soc21_website-cronjob#39, it was decided it's not such a good idea.

Normally, these perma-blocking locked tasks requiring manual checks are only possible if a task crashes the parent process or similar. However, I can see we still have edge cases we are not accounting for and recovering the locks.

I'm guessing you got this lock as a result of an orphaned task (#36436)? Can you share some more information?

If a task fails - like this

Like this #36455

Like this #36455

Thanks that's awesome. I'm on it.

the way I read that thread, Nics point is about unlocking running tasks, not failed tasks.

If a task fails, it is no longer running, you should release the lock and report the failure, allowing the task to run again (and maybe succeed) at a later schedule. All cron job systems do this.

the way I read that thread, Nics point is about unlocking running tasks, not failed tasks.

If a task fails, it is no longer running, you should release the lock and report the failure, allowing the task to run again (and maybe succeed) at a later schedule. All cron job systems do this.

Absolutely, and failed tasks are unlocked. We just have a few scenarios not covered so we aren't catching exceptions where we should be catching them. I'll work on fixing this soon so you can test. ?

ok cool - so the failure case I provided a useful one then

hi
i have similar problem. i get this error:

{
    "success": true,
    "message": null,
    "messages": null,
    "data": {
        "message": "could not acquire lock on task. retry or allow concurrency."
    }
}

i change the
Scheduler config > Task Timeout
to 10 sec, but not any effect. i use shared hosting and can not check linux cron report.

how to resolve the problem?
i use joomla version 5.0.0