Copying and Rerunning a Job

A submitted job never changes, so the way to run it again, or to run a changed version of it, is a new draft made from it. Copy to Draft copies the whole job; Rerun Not-Run Sites makes a draft for only the sites it did not run. Both are in the job's details.

Who Can Make One

Only someone who sees the whole job can copy or rerun it: its preparer, its approver, a Hub administrator, or anyone whose role holds the Jobs grant at every site it reaches. See Jobs Page.

The person who makes the copy or rerun becomes the preparer of the new draft, which then goes through editing, submitting and approval like any other draft. See Preparing a Job and Job Approval.

Copy to Draft

Copy to Draft is offered on every submitted job, whatever its state, including a rejected one. The new draft is named "Copy of" and the job's name, and holds the same steps, import options, limits, tags and configuration file. The tags are turned into sites again when the copy is submitted, so the copy reaches the sites carrying them then.

A copy of a rerun names no tags, because a rerun names sites instead. Tick the tags the copy reaches on its Sites tab before submitting it.

The key password is not copied; enter it again on the Job tab.

Rerun Not-Run Sites

Rerun Not-Run Sites is offered on a finished, stopped or halted job that has at least one site it did not run. The new draft is named "Rerun of" and the job's name, and holds the same steps, import options, limits and configuration file. It names no tags. Its sites are listed one by one, and are only the sites the job did not run:

• Sites shown as offline, not run, not ready, not run (...) or not permitted, not run (...).
• Sites shown as stopped, not run or halted, not run.
• Sites shown as not run: step N never reached the site.

It leaves out sites that finished, failed or ended as unknown, and sites stopped or halted after a step.

The key password is not copied; enter it again. The file stays the same: any file chosen for the rerun must be the same file as the original's, with the same SHA-256, or the Hub refuses it.

A rerun's site list is fixed when it is made. A site can be unticked to leave it out, but no site can be added, and no tag can be ticked (see A Rerun's Sites).

A rerun is a new job. When it reaches more sites than the approval threshold, it needs approval again, even when the original was approved.

Sites Where the New Preparer Lacks the Jobs Grant

A copy or a rerun can reach sites where the person who made it does not hold the Jobs grant, as when it was made from someone else's job. Submitting leaves those sites out, since a job runs only where its preparer holds the grant.