Please note that we use a drilldown into the Windows Task Scheduler (WTS) and we are relying on WTS to trigger those Scheduled Tasks and it's not the other way around.
Thus, it would be more accurate if your sentence is phrased as "SyncBack is no longer being run on schedule" (unless there are errors in profiles/logs).
It sounds like there may be issues with WTS. Try opening WTS
http://support.2brightsparks.com/knowle ... duled-jobs
and check the History tab under the scheduled Task in question for errors or return values. Instructions to access the History tab included here:
http://support.2brightsparks.com/knowle ... uler-fails
It is not unknown for WTS to simply stop triggering Tasks. It may help to solve the issue if you delete and re-create the Task, but it could also be a temporary solution (a classic situation is where deletion/re-creation of Task works once but does not subsequent times). If so, a Windows rebuild may be required. But probably best to see the History tab to find out why WTS has stopped triggering that Task first.
Thus, it would be more accurate if your sentence is phrased as "SyncBack is no longer being run on schedule" (unless there are errors in profiles/logs).
It sounds like there may be issues with WTS. Try opening WTS
http://support.2brightsparks.com/knowle ... duled-jobs
and check the History tab under the scheduled Task in question for errors or return values. Instructions to access the History tab included here:
http://support.2brightsparks.com/knowle ... uler-fails
It is not unknown for WTS to simply stop triggering Tasks. It may help to solve the issue if you delete and re-create the Task, but it could also be a temporary solution (a classic situation is where deletion/re-creation of Task works once but does not subsequent times). If so, a Windows rebuild may be required. But probably best to see the History tab to find out why WTS has stopped triggering that Task first.