diff --git a/website/content/docs/job-specification/reschedule.mdx b/website/content/docs/job-specification/reschedule.mdx
index 97545b2e4cd..dfdf1ed52d5 100644
--- a/website/content/docs/job-specification/reschedule.mdx
+++ b/website/content/docs/job-specification/reschedule.mdx
@@ -78,8 +78,10 @@ they run on every node.
 - `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
   is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
 
-- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is set to true
-  the `attempts` and `interval` fields are not used.
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is
+  set to `true` the `attempts` and `interval` fields are not used. The [`progress_deadline`][]
+  parameter within the update block is still adhered to when this is set to `true`, meaning no more
+  reschedule attempts are triggered once the [`progress_deadline`][] is reached.
 
 Information about reschedule attempts are displayed in the CLI and API for
 allocations. Rescheduling is enabled by default for service and batch jobs
@@ -127,3 +129,5 @@ job "docs" {
   }
 }
 ```
+
+[`progress_deadline`]: /nomad/docs/job-specification/update#progress_deadline