loader detect jobs making no progress neither success nor failure

The deployment in question is running the latest patched 2.3.

A loader job that is scheduled to run every 10 minutes stopped making any progress. We were first alerted to the issue by the status servlet after the default amount of time (52 hours or 3120 minutes) for not finding a success for a loader job.

Inspection of the GROUPER_LOADER_LOG table showed no successes for the job but also no failures. There were no entries for the 52 hours after the last job success.

This is an RFE so that the loader would automatically detect that a loader job is neither succeeding nor failing and determine if it is running/scheduled at all and if not then schedule it again.

That is, we request that the loader recover gracefully from this failure mode.