#109110Introduce scheduler task priority
Description
Currently when multiple scheduler tasks are due to run when the scheduler is invoked it picks the task that is “longest overdue” and no further tie breaker.
That means you can never really ensure that a scheduled task will actually run at the specified time, because on the scheduler run on that time other tasks might be picked first and take long.
If you have a task that is time critical, that is a risk. Imagine you use the workspace publishing task, to publish content at a predefined time but then other tasks are picked first, that index content into solr, clean up the db, index files from the file system or fetch data from an slow API.
The suggestion to mitigate that risk is to introduce a simple High/Medium/Low priority flag for scheduler tasks.
Once selecting the next task to execute the scheduler would choose by priority first, and then “longest overdue” as a tie breaker. This gives the website administrators more control over the execution order and lets the prioritize time critical tasks.
Reviews 4
Related issues 2
History 712
-
Sebastian Michaelsen changed description <span data-processor="relativetime" data-value="2026-02-26T13:49:50+00:00" > 02/26/26, 13:49 </span>
-
Garvin Hicking changed priority
Should haveCould have <span data-processor="relativetime" data-value="2026-02-26T18:58:44+00:00" > 02/26/26, 18:58 </span> -
Gerrit Code Review pushed patch set 1 for main to change 93300 status
NewUnder Review <span data-processor="relativetime" data-value="2026-03-21T21:44:39+00:00" > 03/21/26, 21:44 </span> -
Gerrit Code Review pushed patch set 1 for main to change 93301 <span data-processor="relativetime" data-value="2026-03-21T21:56:17+00:00" > 03/21/26, 21:56 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 93301 <span data-processor="relativetime" data-value="2026-03-21T22:12:31+00:00" > 03/21/26, 22:12 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 93301 <span data-processor="relativetime" data-value="2026-03-22T09:05:08+00:00" > 03/22/26, 09:05 </span>
-
Garvin Hicking changed Related to #109314 <span data-processor="relativetime" data-value="2026-03-22T18:59:21+00:00" > 03/22/26, 18:59 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 93301 <span data-processor="relativetime" data-value="2026-03-23T10:00:17+00:00" > 03/23/26, 10:00 </span>
-
Sebastian Michaelsen commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-03-24T07:05:09+00:00" > 03/24/26, 07:05 </span>Applied in changeset commit:0c74e7d620b99dfaeba6bd4332be3f17f2b9b09a.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-03-31T08:09:12+00:00" > 03/31/26, 08:09 </span> -
Benjamin Franzke changed Related to #110149 <span data-processor="relativetime" data-value="2026-07-03T08:32:42+00:00" > 07/03/26, 08:32 </span>
and what if now all tasks are set to high prio? wouldn’t it be easier to just use a 2nd entry in crontab to trigger the dedicated task?
but just an opinion, feel free to push something