Trouble shooting background processes is difficult. Knowing what exactly the task is that is about to be processed is very important for trace reading.
Currently - even when traced with rtm:3 - when a background scheduler picks up a schedule record, it is not printed into the log file.
So the idea is:
When scheduler picks up a schedule record for processing, it should be printed into the log in rtm:3 traces.
It would be just as useful as the SCRIPTTRACE messages printing parameter values when calling JS from RAD execution.