BigBlueButton is a blocker in upgrade to 4.0

Preparation Create a new BigblueButton activity B1: Create a recording by joining the course and recording for at least 10 seconds. End the meeting. Run the cron Ensure that the recording is displayed on the room page Look into the mdl_bigbluebuttonbn table and fetch meetingid, courseid and id values for the current activity. Then add the following log into the mdl_bigbluebuttonbn_logs table:   INSERT INTO mdl_bigbluebuttonbn_logs (courseid, bigbluebuttonbnid, userid, timecreated, meetingid, log, meta) VALUES (<courseid>, <bbbid>, 2, 1648585713, '<meetingid>' , 'Create' , '{\"record\":true}' ); Run the script: Now run the cli script and force the recovering of the recording: php mod/bigbluebuttonbn/cli/migrate_recordings.php -f It should go through all previous logs and bigbluebutton activities and fetch missing recordings. Processing BigbluebButton Test completion(id:2), in course Completion Test(id:3).... ->No meetings logs found... .... Processing BigbluebButton B1(id:XXX), in course C1(id:4).... ->Processing meeting ID XXXXXX ...recordingsExecuting mod_bigbluebuttonbn\task\upgrade_recordings_task for meeting XXXXXX... Tests: Ensure that the activity displays the recording Ensure that the script mentions the activity as "Processing meeting ID"..