Review main Merged

93301[FEATURE] Introduce scheduler task priority

Sebastian Michaelsen CR +2 V +2 Normal +196 −2 updated 03/24/26, 07:02

Commit message

Add a `priority` column (High=150, Regular=100, Low=50) to
`tx_scheduler_task` so administrators can control execution order.
The scheduler picks the highest-priority due task first, using
`nextexecution ASC` as a secondary tiebreaker.

The priority field appears in the Timing tab of every task type's
editing form and as a column in the scheduler backend module list
view. Third-party extensions can register additional priority levels
via a standard TCA override; labels are resolved dynamically from
TCA so custom values display correctly without further changes.

Functional tests cover priority ordering and nextexecution
tiebreaking in SchedulerTaskRepository::findNextExecutableTask().

Review

  • Code review CR +2 Done
    • Garvin Hicking +2
    • Josua Vogel +1
  • Verified V +2 Done
    • Garvin Hicking +2
    • Josua Vogel +1
    • core-ci +1 CI

Issues 1

Files 8

Review log 1317

  1. Sebastian Michaelsen uploaded patch set 1 03/21/26, 21:56

  2. core-ci voted on patch set 1 V -1 03/21/26, 22:10 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/98361

  3. Sebastian Michaelsen uploaded patch set 2 V -1 03/21/26, 22:12

  4. core-ci voted on patch set 2 V +1 03/21/26, 22:21 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/98362

  5. Garvin Hicking commented on patch set 2 03/22/26, 06:35

    I think this pragmatic approach could cover use cases. A solution that generates/calculates more complex execution orders (based on before/after definitions) would raise complexity a lot. Maybe this patch would for the future allow to create parallel "scheduler pipes", so one run for high prio tasks (every minute) and a low prio scheduler (every hour).

    SchedulerTaskRepository.php:537

    We should utilize TCA Schema API here

    tx_scheduler_task.php:73

    For new fields we should use the "scheduler.tca:tx_scheduler_task.priority" label notation (also below)

    TaskList.fluid.html:265

    Maybe to prevent the table that already spans too wide with a new cell, and add priority below frequency as an information? Maybe even with an info pill layout?

    ext_tables.sql:4

    Theoretically this could be auto-created, did you test as what it gets created? Numbers would be good so extensions could add their own numbers via TCA Override
  6. Sebastian Michaelsen uploaded patch set 3 V +1 03/22/26, 09:05

  7. Sebastian Michaelsen commented on patch set 2 03/22/26, 09:05

    SchedulerTaskRepository.php:537 Reply

    Done

    tx_scheduler_task.php:73 Reply

    Done

    TaskList.fluid.html:265 Reply

    Done

    ext_tables.sql:4 Reply

    Done
  8. core-ci voted on patch set 3 V +1 03/22/26, 09:15 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/98378

  9. Garvin Hicking voted on patch set 3 CR +1 03/22/26, 11:07

  10. Benni Mack commented on patch set 3 03/22/26, 15:52

    scheduler_file_storage_extraction_task.php:50

    hey, I Have an idea, let's move the execution_details, next_execution, and last_execution into one palette (in a prepatch). then we can just add priority to all fields
  11. Sebastian Michaelsen uploaded patch set 4 CR +1 V +1 03/23/26, 10:00

  12. Sebastian Michaelsen commented on patch set 4 03/23/26, 10:00

    scheduler_file_storage_extraction_task.php:50 Reply

    Done
  13. core-ci voted on patch set 4 V +1 03/23/26, 10:39 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/98446

  14. Garvin Hicking voted on patch set 4 CR +1 V +1 03/23/26, 11:19

  15. Josua Vogel voted on patch set 4 CR +1 V +1 03/23/26, 11:46

  16. Garvin Hicking voted on patch set 4 CR +2 V +2 03/24/26, 07:02

  17. Garvin Hicking merged patch set 5 03/24/26, 07:02