TYPO3 Scheduler Guide: How to Set Up and Manage Cron Jobs in 2026
If you want to understand the TYPO3 Scheduler from the basics to more advanced use, this guide will help you learn how it works for Scheduler tasks, cron job setup, and Symfony console commands. It explains how TYPO3 makes task automation simple, reliable, and useful for smoother website maintenance.
What is TYPO3 Scheduler?
TYPO3 Scheduler is a built-in tool that allows admins and developers to schedule tasks inside TYPO3. These tasks can run hourly, daily, weekly, or at custom intervals depending on the website’s needs.
It is useful for both simple maintenance jobs and advanced automation workflows using Symfony console commands.
How TYPO3 Scheduler Works
TYPO3 Scheduler does not run automatically on its own. It needs a server-side trigger like a cron job, Windows Task Scheduler, hosting panel cron, or systemd timer.
Cron starts the Scheduler command, and TYPO3 checks which tasks are ready to run. If a task is due, TYPO3 executes it and records the result in logs.
Basic Flow
A task is created in TYPO3
A schedule or interval is assigned
Cron triggers the Scheduler command
TYPO3 checks due tasks
Tasks are executed one by one
Logs show success or errors
TYPO3 Scheduler and Cron Jobs
TYPO3 Scheduler manages the tasks, while cron triggers them at fixed intervals. One cron job can run all scheduled TYPO3 tasks, so there is no need to create separate cron jobs for every task.
For Composer-based TYPO3 projects, the Scheduler command is usually:php vendor/bin/typo3 scheduler:run
For non-Composer projects, the command may look like:php typo3/sysext/core/bin/typo3 scheduler:run
Manual Run vs Automatic Run
Manual Run
Manual execution is useful for testing, debugging, or running urgent maintenance tasks. Admins can run Scheduler tasks from the TYPO3 backend or through CLI.
Automatic Run
Automatic execution is done through cron or another server trigger. This is the best option for live websites because it runs tasks regularly without manual effort.
Common TYPO3 Scheduler Tasks
TYPO3 Scheduler is commonly used for:
Cache cleanup
Database optimization
Log cleanup
File cleanup
Newsletter sending
Search index updates
Garbage collection
Import and export jobs
Custom maintenance tasks
These tasks help keep the website clean, fast, and reliable.
Useful Scheduler CLI Commands
TYPO3 provides helpful commands for running and testing Scheduler tasks.
Run all due tasks:vendor/bin/typo3 scheduler:run
Run a specific task:vendor/bin/typo3 scheduler:run --task=1
Force a task to run:vendor/bin/typo3 scheduler:run --task=1 -f
Run in verbose mode for debugging:vendor/bin/typo3 scheduler:run --task=1 -v
These commands are helpful when checking whether a task is working correctly.
Setting Up TYPO3 Scheduler
In most TYPO3 installations, Scheduler is available as a core extension. If it is not active, it can be enabled from the TYPO3 backend or installed through Composer.
For Composer installation:composer require typo3/cms-scheduler
After activation, check the Scheduler module in the backend and run the setup check before adding live tasks.
Important Setup Checks
Before using Scheduler on a live website, check:
Correct PHP CLI path
Proper file permissions
Scheduler extension status
Cron command accuracy
Task frequency
Email notification settings
TYPO3 logs and server logs
A proper setup helps prevent failed tasks and unexpected issues.
Task Groups in TYPO3 Scheduler
Task groups help organize scheduled tasks by purpose. For example, you can create separate groups for cache cleanup, database maintenance, newsletters, file cleanup, and logs.
This makes the Scheduler easier to manage, especially on large TYPO3 websites with many automated tasks.
Custom Tasks with Symfony Console
Since TYPO3 supports Symfony console integration, developers can create custom commands and run them through Scheduler.
This is useful for advanced workflows such as data imports, report generation, content sync, cleanup jobs, and custom automation.
Before using a custom command in production, it should always be tested through CLI and checked in a staging environment.
Common Scheduler Problems
Some common TYPO3 Scheduler issues include:
Cron not running
Wrong PHP CLI path
Task disabled
Permission problems
Task scheduled for a future time
Stuck or overlapping tasks
Missing logs or email notifications
Most problems can be fixed by testing the command manually, checking permissions, and reviewing TYPO3 logs.
Best Practices for TYPO3 Scheduler
Use sensible task intervals and avoid running heavy jobs too often. Important tasks can run more frequently, while cleanup and database tasks can run less often.
Keep task groups organized, monitor logs regularly, and avoid unnecessary parallel execution unless the task is safe to run that way. Always use proper permissions for cron users to keep the setup secure.
Conclusion
TYPO3 Scheduler is a useful tool for automating regular website tasks and reducing manual maintenance. When it is configured with the right cron setup, task frequency, permissions, monitoring, and custom command handling, it helps keep TYPO3 websites clean, stable, and easier to manage.
