Job scheduling vs. workload automation
One of the most important differences between a job scheduler and workload automation is the ability to automate error resolution. Beyond simply automating your job scheduler, workload automation has a much higher level of intelligence to actively solve problems during task execution.
For example, let’s say you want to backup your database at 2 a.m., but your database backup folder is out of space. A job scheduler will attempt the task and fail when it finds the folder full. It will not complete the task, leaving you to discover the failure in the morning — or to receive a late-night call from a panicked employee.
By contrast, if you run workload automation, the system will kick off an error recovery workflow to expand the available drive space on the server. Then, it will try the task again and continue to iterate the server expansion step until it opens up enough space to complete the backup job. The workload automation solves the problem using intelligent workflows so that you can arrive in the morning with the task completed.
Returning back to the analogy of the alarm clock, the job scheduler is like a typical radio alarm clock. It plays whatever radio station it’s tuned to, even if that station produces dead air. If the clock is enhanced with workload automation, it will detect the silence and automatically change the channel to something that can actually wake you up.