Grouper report incorrectly reports NON-SUCCESS for in progress jobs

Grouper report will show "NON-SUCCESS" for jobs that are "in progress" at the time of the report run.
 
Example: 
"
----------------
LOADER JOBS WITH NON-SUCCESS
----------------
 
job:               MAINTENANCE__grouperReport
status:            STARTED, started: 2020-12-04 07:00:00.0 ()
ins/upd/del/tot:   0/0/0/0
error:             null
"

The report is run daily at 07:00. The most common offender is the 'MAINTENANCE_grouperReport', but other jobs that also start at the same time of the report show up from time to time too. ( including custom jobs and other "built in jobs" like: MAINTENANCE_rules , OTHER_JOB_timeDaemon, etc...)

I suggest the two approaches be taken to improve the usefulness/accuracy of the report.

1) "error: null" should be reported as "unknown" instead of "NON-SUCCESS" ( or maybe reported as "in progress" instead of based on any "completion status".

And it would also be useful if...

2) The report job could "sleep ( a new config value?) and check those jobs again" to try to give the "in progress jobs" sometime to complete. Yet, they still could be "unknown" after the sleep too. And that might be a good error condition to report.