Job Retention¶
The Hub keeps a job's uploaded configuration file and its record for as long as it keeps the statements the job's steps were sent with. A cleanup on the Hub deletes what is past that period once a day. The key password goes as soon as the job ends.
The Configuration File¶
The Hub keeps a job's configuration file encrypted in its database for as long as it keeps the job's record, so the job can be reviewed, its contents viewed and its not-run sites rerun without uploading the file again. A draft, and a job that has not ended, keep their file until the job ends or the draft is deleted; the cleanup never deletes them.
Each job keeps its own copy of its file, so a copy or a rerun of a job holds a second copy. A file can be up to 190 MB. With Statement Retention (days) empty, the default, the Hub never deletes an ended job's file.
The key password goes earlier: the Hub deletes it as soon as a job ends. A copy or a rerun needs it entered again; see Copying and Rerunning a Job.
The Job's Record¶
A job's record holds its steps, its sites and each site's results, its approval, its file's name, hash and contents, and any rollbacks. It stays as long as the Hub keeps its signed statements, set by Statement Retention (days) in the Jobs and Statements section of System Administration -> Hub Configuration (see Job Approval Threshold and Statement Retention):
| Value | Effect |
|---|---|
| Empty (the default) | Signed statements, and the jobs that refer to them, are kept |
| A number of days, 1 or more | The cleanup deletes signed statements older than this, and the records and files of jobs that ended longer ago than this |
A job that has not ended is never deleted this way. Nor is a job with a rollback the Hub has not yet sent or the site has not yet answered: the cleanup deletes it on a later night, once the rollback ends. Rolling back a site, copying the job and rerunning it all need its record, so they stay available as long as it does.
The Hub's Signed Statements¶
The Hub records every statement it signs in its own database before sending it, so it has a record of every action it vouched for even when the send fails. It also writes each one to hub-audit.log; see Access Control and Audit Log. Statement Retention (days) applies to the database record only, not to the log file.
Each site keeps its own record of the statements it received, for the period its own MCP settings set; see What a Site Records for a Job.
Jobs and Disaster Recovery¶
Jobs, their files and the Hub's signed statements are runtime data. They are not part of the Hub's configuration export and are not restored with it. The Approval Threshold (sites) and Statement Retention (days) settings are part of the configuration, and a configuration import that changes either one writes a Hub audit entry naming who ran it and the values before and after. See Hub disaster recovery.