Review main Ready for review

97609[FEATURE] Show progress of scheduled commands

Benni Mack CR +1 V +1 Hard +532 −2 updated 11/20/26, 16:30

Commit message

Symfony commands executed as scheduler tasks can now report their
progress, which is shown as progress bar in the Scheduler module and
in the output of "scheduler:list".

A command implements the new ProgressReporterAwareInterface and
receives a TaskProgressReporter bound to the executed task. The
reporter persists the progress in the system registry, as the module
reads it in a different process than the one running the command.
Writes are limited to changes of at least one percentage point, so the
reporter can be called for every processed item.

ExecuteSchedulableCommandTask now implements the existing
ProgressProviderInterface and reads the persisted value. The value is
removed when the command finishes, when a running task is stopped, or
when an execution exceeding the maximum lifetime is discarded.

Test this change

Run a command in your clone of the TYPO3 Core. Then try what the change does and vote on Verified in Gerrit. How to review a patch

Check out patch set 1
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/09/97609/1 && git checkout FETCH_HEAD
Cherry-pick onto main
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/09/97609/1 && git cherry-pick FETCH_HEAD

Review

  • Code review CR +1 Needs a vote
    • Josua Vogel +1
    • Fabien Udriot +1
  • Verified V +1 Needs a vote
    • Josua Vogel +1
    • core-ci +1 CI

Merge conflicts 2

Issues 1

Files 12

Review log 45

  1. Benni Mack uploaded patch set 1 11/13/26, 11:16

  2. core-ci voted on patch set 1 V +1 11/13/26, 11:23 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/114310

  3. Fabien Udriot voted on patch set 1 CR +1 11/13/26, 12:12

  4. Josua Vogel voted on patch set 1 CR +1 V +1 11/16/26, 10:45

  5. Garvin Hicking commented on patch set 1 11/20/26, 16:30

    Unresolved

    Could you describe why you chose sys_registry for its "persistence"? Haven't run this through Claude (no more cookies^Wtokens for me today) - but this feels like it can cause issues for two instances of a task running in parallel? Can't we directly persist this to tx_scheduler_task.execution_details[progress]?