HTCondorWiki: Job Class Ad Flow

 
 The starter sends periodic updates to the startd so that the startd can use updated attributes when evaluating its policy.  Failed updates are simply dropped.  The update interval is controlled by the same knobs that control updates from starter to shadow.
 
+There is a final update from the starter to the startd when the job is done.  If this fails, it is simply dropped.
 
 {subsection: shadow --> schedd}
 
@@ -44,6 +45,13 @@
 
 When the job is finished, the shadow does a final update to the schedd.  If this update fails, the shadow will wait and retry.  This behavior is controlled by SHADOW_JOB_CLEANUP_RETRY_DELAY (30s) and SHADOW_MAX_JOB_CLEANUP_RETRIES (5).  In case of failure even after all retries have been attempted, the shadow exits with a failure code that causes the job to be requeued and (usually) run again.
 
+{subsection: schedd --> history}
+
+The schedd dumps the job ad into the (optional) history file when the job leaves the queue.  If this fails, it is simply dropped.
+
+{subsection: startd --> history}
+
+When a claim is deactivated (i.e. starter exits), the startd writes its copy of the job ad into the startd's (optional) history file.  If this fails, it is simply dropped.
 
 {subsection: qedit --> schedd}