diff --git a/17/umbraco-cms/reference/configuration/distributedjobssettings.md b/17/umbraco-cms/reference/configuration/distributedjobssettings.md
index e9dcfb4fe1c..58b9d6b769a 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 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.