Occasionally when administering a Concrete website, you’ll need to run administrative, maintenance actions that might take awhile. This might be something simple like clearing the cache, or something more extensive like regenerating the site’s sitemap.xml file, reindexing page content or deleting old versions of pages.
Tasks are these maintenance actions. Tasks can be triggered from the Concrete backend Dashboard, or from the command line. Tasks can also be scheduled through the Dashboard, provide their own logging, and can be constructed in such a way that they do their work in queueable batches.
In Concrete 8 and earlier, this functionality was fulfilled by Jobs. Jobs still function in Concrete 9, but Tasks offer a number of improvements over jobs, which is why they’re the much preferred method of offering this kind of functionality going forward.