This is not an error, in fact I looked at all my machines and it's in the CL5.log for all of them. I did some digging and what appears is happening is that once a job successfully completes, CL5 looks at the windows task scheduler just to make sure there are no jobs relating to the deployment there. If there are no jobs in the windows task scheduler, CL5 gives this message.
Very nice explanation.
Thank YOU, Kevin.