from what i can argue from your images , the task Extensions update notification is causing the stop

@alikon What is your argument for that assumption?

look at man run icon near the task

@alikon You're probably right! I disabled the Extension Update Notification task. After that, I was able to test-run the other three tasks. I'll check whether they will run again.

If they do, I will close this issue and open an issue with the developer of the Extension Update Task.

Thanks for taking the time to look at the issue!

On a different site, I have the same issue. But on this site, the standard Joomla Update Notification was hanging for weeks, and I have not been able to restart it.

can you click on the man running icon ?

When I click on the icon, it's gone. But when I try to test-run the task, I get the error message: "No content was returned".

Just an idea: Shouldn't we have a kind of "janitor" that does something like a "garbage collection"? To periodically stop tasks that have gone crazy, timed out, or do have other issues.

@dautrich Is it OK to give us access to the site ? Would love to take a look to see why the task Update Notification could not finish it's execution like that (result in No content was returned error). I guess because that reason, the task could not be finished and prevent the next tasks to be executed.

@joomdonation
It's a bit difficult to give you access to the respective site. I need the site urgently. Therefore, I deleted the “hanging” task and re-created it. This resolved the situation (at least temporarily).

I will try to kickstart one of my backups (taken during the period the task was hanging) to a test site. If the restored site shows the same behavior, I can create a superuser account for you on that test site.
Would that be sufficient, or will you require FTP access as well?

OK, thanks @dautrich, super user account is enough. Just so you know, with a super user account, I can install a Files Manager extension to add some debug code to check the issue if needed.

@joomdonation
I have kickstarted a backup of my site to a test site: [https://www.upgrade.hasenritter.de]
You can find the “hanging” task on the restored site as well.

There is a superuser account which you can use:

• Username: ciaran
• Password: Start1234567 (pls change to a secure password of your own)

Hmm. The account seems to be invalid. And you should not post super user account here as it could be seen by everyone. Could you please send me an email to tuanpn@joomdonation.com for further communication?

@joomdonation
Pls try again.
For your information: Password reset is required for that account, and I track that user's activities. (Btw: I saw your failed login attempts.) Anyway, it's only a test site, which I will purge as soon as your activities have finished.

@joomdonation
The real site has .htaccess protection for the admin directory and MFA for my own superuser account. Since there is an SSL certificate on the test site, you might use MFA for your activities as well.

Thanks @dautrich. I was able to login. Will try to check to see if I can figure out the reason of the issue.

@dautrich I tried on your test site but could not see the issue. When I run the task manually by clicking on the Run Test button, the task is executed properly, no error No content was returned as you mentioned. As of right now, I do not have any clue why the error happens yet, will try to look more at Scheduled Tasks later.