Glossary
Scheduler
The task scheduling of TYPO3, for everything that should happen regularly and without anyone doing it.
What the Scheduler is for
Some things should happen regularly without anyone clicking: a data import from another system, clearing out old logs, sending a newsletter, refreshing a Solr index.
The Scheduler manages those tasks with an execution time and a log. What it does not do is start itself. That requires a cron job on the server that calls it at regular intervals.
The most common source of trouble
Most installations come to grief at exactly that division. In the backend the tasks are cleanly set up and given a schedule, and nobody calls them, because the cron job is missing, went astray during a server move, or runs under the wrong conditions.
It is a silent fault: the website works, and only things nobody actively misses are absent. Until somebody asks why the product data has been weeks out of date.
Monitoring is part of it
So we treat scheduled tasks as part of operations rather than as a setup step. Anything somebody relies on gets an alert, and one that fires when execution stops as well, not only on errors.
There is more on this under TYPO3 maintenance.