As a follow up of MDL-80061 and MDL-76339, we need to see if there is not a better way to handle the recording dismissal.

The process of marking recordings as dismissed is the following:

• BBB module will try to get the recording information
• If it fails outside the recording time limit period of 30 days, it will "dismiss" the recording (this will prevent from sending too many request that are deemed to fail).

We need to review this process as there were instances where getRecordings fails due to a networking issue, it's being interpreted as recordings no longer existing in Moodle.  and marked as state=1 , which causes them to disappear to users. A better approach would be perhaps to ignore empty responses (or at the very least not make any DB changes based on them) and only proceed with making recording status changes if we are sure we have a valid response. That way in the event of network connectivity issues, we hold off on changing the status until we can verify what is/isn't on the server.

Currently a workaround to re-enable those records is to regulary (through a dedicated cron task) run CLI script mod/bigbluebuttonbn/cli/update_dismissed_recordings.php which does not use time filtering.