Stopping a task in the Scheduler backend module 

As was explained above, a task is marked as being executed while it is running. If the process running the task crashes or is killed for some reason, the task will stay marked as being executed. This will be cleaned up automatically according to the maximum lifetime parameter (also described previously), but this may be inconvenient in some circumstances.

Stopping a task

Stopping a running task from the main screen

In such cases it is possible to use the "stop" button to clean up marked executions for the given task. This will make it possible to run this task again. However please note that this will not kill a corresponding still running or continuously hanging process.

Note: This does not terminate an actual running or hanging process.

Stopping a task via console command 

You can also use a command to stop the task:

# Note the id of the task
vendor/bin/typo3 scheduler:list

vendor/bin/typo3 scheduler:run --task=<taskUid> --stop
Copied! 
# Find the id of the task
typo3/sysext/core/bin/typo3 scheduler:list

typo3/sysext/core/bin/typo3 scheduler:run --task=<taskUid> --stop
Copied!

How to handle a truly "hung" task 

If a task hangs or is stuck (for example due to an infinite loop or external I/O), then stopping it via TYPO3 (either UI or CLI) will only clear TYPO3’s internal flag.

But the actual PHP process that’s running the task will continue on the system until it finishes or the OS/PHP process manager kills it.

If a task keeps running indefinitely:

  1. Identify the process (via ps, top, or your process manager — for example, systemd or cron).
  2. Manually terminate the PHP process (for example, kill <pid>).
  3. Then run: typo3 scheduler:run --task=<taskUid> --stop
ps aux | grep scheduler

# you might find something like this:
www-data  12345  99.0  5.2  php vendor/bin/typo3 scheduler:run

# To force-stop that OS-level process:
sudo kill 12345

# Then clear the mark again via:
vendor/bin/typo3 scheduler:run --task=13 --stop
Copied!