it might have been a one off
or it might have been related to the new faster history catch up routine
was there any error under view, program event log?
try it again maybe
it might have been a one off
or it might have been related to the new faster history catch up routine
was there any error under view, program event log?
try it again maybe