From 6a921902bdd6e577d7c8824702e1c4dede5f717b Mon Sep 17 00:00:00 2001 From: mole Date: Wed, 10 Dec 2025 10:59:38 +0100 Subject: [PATCH 1/2] Add MaximumExecutionTime setting documentation for distributed jobs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Documents the new MaximumExecutionTime setting that was added in umbraco/Umbraco-CMS#21100. This setting specifies when a running distributed job is considered stale and can be recovered by another server. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 --- .../configuration/distributedjobssettings.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/17/umbraco-cms/reference/configuration/distributedjobssettings.md b/17/umbraco-cms/reference/configuration/distributedjobssettings.md index e9dcfb4fe1c..3a6b0ec31e6 100644 --- a/17/umbraco-cms/reference/configuration/distributedjobssettings.md +++ b/17/umbraco-cms/reference/configuration/distributedjobssettings.md @@ -8,7 +8,8 @@ The distributed jobs settings allow you to configure how Umbraco handles distrib "CMS": { "DistributedJobs": { "Period": "00:00:05", - "Delay": "00:01:00" + "Delay": "00:01:00", + "MaximumExecutionTime": "00:05:00" } } } @@ -29,3 +30,11 @@ A shorter period means jobs are picked up more quickly, but increases the freque **Default:** `00:01:00` (1 minute) Specifies how long the server should wait after initial startup before beginning to check for and run distributed background jobs. This startup delay ensures that the application is fully initialized and stable before participating in distributed job processing. + +### MaximumExecutionTime + +**Default:** `00:05:00` (5 minutes) + +Specifies the maximum time a distributed job can run before it is considered stale. Jobs that are currently being executed by another server are not picked up by other servers, preventing duplicate execution. However, if a job exceeds this time threshold, it is considered abandoned and can be picked up by another server for recovery. + +This setting is useful for handling scenarios where a server crashes or becomes unresponsive while processing a job. By setting an appropriate maximum execution time, the system can automatically recover and reassign stale jobs to healthy servers. From 076feef384422e60416d4e03466d798c27f1fe81 Mon Sep 17 00:00:00 2001 From: Mole Date: Fri, 12 Dec 2025 13:58:40 +0100 Subject: [PATCH 2/2] Update 17/umbraco-cms/reference/configuration/distributedjobssettings.md Co-authored-by: sofietoft --- .../reference/configuration/distributedjobssettings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/17/umbraco-cms/reference/configuration/distributedjobssettings.md b/17/umbraco-cms/reference/configuration/distributedjobssettings.md index 3a6b0ec31e6..58b9d6b769a 100644 --- a/17/umbraco-cms/reference/configuration/distributedjobssettings.md +++ b/17/umbraco-cms/reference/configuration/distributedjobssettings.md @@ -35,6 +35,6 @@ Specifies how long the server should wait after initial startup before beginning **Default:** `00:05:00` (5 minutes) -Specifies the maximum time a distributed job can run before it is considered stale. Jobs that are currently being executed by another server are not picked up by other servers, preventing duplicate execution. However, if a job exceeds this time threshold, it is considered abandoned and can be picked up by another server for recovery. +Specifies the maximum time a distributed job can run before it is considered stale. Jobs that are currently being executed by one server are not picked up by other servers, preventing duplicate execution. However, if a job exceeds this time threshold, it is considered abandoned and can be picked up by another server for recovery. This setting is useful for handling scenarios where a server crashes or becomes unresponsive while processing a job. By setting an appropriate maximum execution time, the system can automatically recover and reassign stale jobs to healthy servers.