The last run time of scheduled tasks is not persisted correctly. The symptom is that a task runs(starts) on a regular schedule ( ie. weekly) and may have a last run time that is much farther in the past than the actual last start of the task.
When a task is started and then running while Nexus is stopped, then on restart
- last run time shows when that task was last started
- last result duration will be time of server shutdown ( or very close to it) minus last start time
- last result will NOT be "Ok" since the task was abruptly stopped while running by server shutdown. Error may not be good enough either. Need a state that suggests task was forcibly stopped, not by a request from the UI or REST call, but server shutdown, clean or otherwise.