-
Bug
-
Resolution: Fixed
-
Minor
-
4.1.9, 4.2.6, 4.3.3, 4.4
-
MOODLE_401_STABLE, MOODLE_402_STABLE, MOODLE_403_STABLE, MOODLE_404_STABLE
-
MOODLE_402_STABLE, MOODLE_403_STABLE
-
mdl80598-401
-
mdl80598-403
-
mdl80598-master
-
We've found occasionally we get a few stuck adhoc tasks which fail because either the user or the course module they are referencing does not exist anymore (presumably deleted)
Example:
Adhoc task failed: mod_bigbluebuttonbn\task\completion_update_state, Invalid module ID: {$a}Backtrace: line 252 of /mod/bigbluebuttonbn/classes/local/proxy/bigbluebutton_proxy.php: call to get_course_and_cm_from_instance() |
Adhoc task failed: mod_bigbluebuttonbn\task\send_recording_ready_notification,mod_bigbluebuttonbn\task\base_send_notification::get_instance(): Return value must be of type mod_bigbluebuttonbn\instance, null returned |
line 182 of /mod/bigbluebuttonbn/classes/task/base_send_notification.php: call to mod_bigbluebuttonbn\task\base_send_notification->get_instance() |
The tasks should ideally check if the module or user exists at all, and if not then just exit early (since there is nothing to do)
It is fairly involved to recreate this since you need a functioning site, but I think the problem is easy enough to understand that it is not necessary.
- caused a regression
-
-
- Closed
-
