Howard Miller

It's easy enough to write a query to run from cron and clean up the table. Of course, the nature of the beast is that they will return as there continues to be activity in the courses these users are enrolled in. Of course, the real fix is to delete the users from Moodle. But that throws up issues of data retention and the like.

As it stands, if one does nothing, these tasks build up to swamp all others. The adhoc task queue eventually is doing nothing but attempting to contact long lost users and can't do legitimate tasks any more.

So my assertion is that retrying adhoc tasks forever (even with a one day delay) sounds like a bug. Or my site is broken.

I have good intentions to have a look at what the code does but haven't had the time. I was posting just in case somebody has been here before. The lazy approach

It's *highly* unlikely that the URL you have given points to a Moodle site.

In other news, we are NOT your support team for whoever cyberforce is. This is the Moodle community site where the software is discussed. 

Here's another one (the one I use for development on a Mac). There's a Windows version too. I recommend it... for development. There are more obvious production hypervisors for "live" sites...

https://multipass.run/