Execute scheduled task
Moodle version 4.5.4, php 8.1. The scheduled task returns this error.
"Complete a scheduled task: Download an available H5P content type from h5p.org (core\task\h5p_get_content_types_task)
... started at 17:42:01. The current memory usage is 54.7 MB.
Debugging temporarily increased due to a failure delay of 60
... 0 database queries
were used... 300.08128881454 seconds were used.
Scheduled task failed: Downloading available H5P content types from h5p.org (core\task\h5p_get_content_types_task), An incorrect response value was detected. (The operation ended after 300,000 milliseconds, 15915 of 89668 bytes were received)
Debugging information:
The operation was completed after 300,000 milliseconds, 15915 of 89668 bytes were received.
Stack tracing:
* line 410 of the file /lib/classes/cron.php : calling core\task\h5p_get_content_types_task->execute()
* line 208 of the file /lib/classes/cron.php : calling core\cron::run_inner_scheduled_task()
* line 125 of the file /lib/classes/cron.php : calling core\cron::run_scheduled_tasks()
* line 186 of the file /admin/cli/cron.php : calling core\cron::run_main_process()"
CURL request before h5p.org everything is working correctly, the certificates are also correct, everything worked before, how can I fix this?
otacke
Tue, 02/03/2026 - 21:17
Permalink
The scheduled task is a
The scheduled task is a feature of Moodle's own H5P integration, so under MoodleHQ's control. It's not something that H5P Group created, even though they host the server that is talked to.
By default, that scheduled task triggers on the 1st of a month to download the latest versions of H5P content types. Nobody changes that default. So, on the first of every month, all Moodle instances with that scheduled task running essentially form a kind of denial of service attack on the tiny server that was never intended to cope with the vast amount of concentrated requests that it receives.
I assume that what you experience is merely a white flag that the server is raising.