Merge pull request #239674 from IsmailMitchell/docs-editor/iot-hub-devguide-jobs-1685470596

adding job TTL

Author: prmerger-automator[bot]

articles/iot-hub/iot-hub-devguide-jobs.md

@@ -24,7 +24,7 @@ Consider using jobs when you need to schedule and track progress any of the foll
 
 ## Job lifecycle
 
-Jobs are initiated by the solution back end and maintained by IoT Hub. You can initiate a job through a service-facing URI (`PUT https://<iot hub>/jobs/v2/<jobID>?api-version=2021-04-12`) and query for progress on an executing job through a service-facing URI (`GET https://<iot hub>/jobs/v2/<jobID?api-version=2021-04-12`). To refresh the status of running jobs once a job is initiated, run a job query.
+Jobs are initiated by the solution back end and maintained by IoT Hub. You can initiate a job through a service-facing URI (`PUT https://<iot hub>/jobs/v2/<jobID>?api-version=2021-04-12`) and query for progress on an executing job through a service-facing URI (`GET https://<iot hub>/jobs/v2/<jobID?api-version=2021-04-12`). To refresh the status of running jobs once a job is initiated, run a job query. There is no explicit purge of job history, but they have a TTL of 30 days. 
 
 > [!NOTE]
 > When you initiate a job, property names and values can only contain US-ASCII printable alphanumeric, except any in the following set: `$ ( ) < > @ , ; : \ " / [ ] ? = { } SP HT`
@@ -217,3 +217,5 @@ Other reference topics in the IoT Hub developer guide include:
 To try out some of the concepts described in this article, see the following IoT Hub tutorial:
 
 * [Schedule and broadcast jobs](schedule-jobs-node.md)
+
+