Background processing for assignment module fails to run

Background processing for assignment module fails to run

by Andy Nicolle -
Number of replies: 2
Email notifications of assignments being graded delayed in their sending (often several hours later), I have found that the scheduled task 'Background processing for assignment module' failing is what is causing the delay. When the scheduled task is run manually via command line the emails are sent, but with the below error message:

Execute scheduled task: Background processing for assignment module (mod_assign\task\cron_task)
Processing 10 assignment submissions ...
Processing assignment submission 4962 ...
!!! Exception - Cannot access private property cm_info::$uservisible !!!

When viewing the scheduled task logs for the specific task the below message is shown:

Execute scheduled task: Background processing for assignment module (mod_assign\task\cron_task)
... started 15:38:30. Current memory use 18.8MB.
Processing 10 assignment submissions ...
Processing assignment submission 4966 ...
... used 11 dbqueries
... used 0.15214896202087 seconds
Scheduled task failed: Background processing for assignment module (mod_assign\task\cron_task),Cannot access private property cm_info::$uservisible
Each time the task runs the fail delay increases by 60.

Ubuntu 18.04
PHP 7.2

Any help would be appreciated in getting this ask to run regularly again.
Andy
Average of ratings: -
In reply to Andy Nicolle

Re: Background processing for assignment module fails to run

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
Switch on Debugging right up to Developer and let's get a full trace.

When did this start? My guess would be a problem with an upgrade (e.g. files overwritten rather than replaced)
In reply to Howard Miller

Re: Background processing for assignment module fails to run

by Andy Nicolle -
It has only recently been reported, but it probably started with an upgrade to 3.9.6. It also looks like a minor version upgrade to 3.9.7 has corrected the issue.

Thank-you for replying to the initial query.