BE module list dies if a tasks class cannot properly be unserialized
This happened not the first time to me today, that the scheduler backend module throws just a white page. We could always solve this by cleaning out the task-records from the scheduler tasks table in the database.
Make it a bit more robust to detect this problem, show a warning message
#1 Updated by Francois Suter over 5 years ago
- Status changed from New to Accepted
- Assignee set to Francois Suter
Indeed this was improved already in the past, but apparently not enough. One typical situation is if a task's class signature has changed since it was first serialized.
I'll try to take a look at some point.
#3 Updated by Mario Rimann about 5 years ago
Francois Suter wrote:
I finally took a look and I couldn't trigger such a mishap. Could it be related to #33116? Could you provide a test scenario?
I don't think it's directly related to #33116 by reading the bug report.
Also I'm not 100% sure what triggered the error. But I think it was one of the following:
- the scheduler task's class was removed (and the task record still points to it)
- the scheduler task's class was renamed (and the task record still points to the old name)