Restart a Gigadock Job That Stopped Due to Cost

Context

If a Gigadock job stops due to exceeding the cost threshold set for the run, a Restart collection will be created by the job. This How-to Guide explains how to use the Restart collection to complete the run.

Procedure

Go to the Jobs Tab of the Gigadock job that stopped due to exceeding the set cost threshold.
Click the “Rerun” button to open the Job Form and make the following adjustments:
- Under Inputs: Alternate, clear the Input Conformer Dataset parameter if it was set.
- Under Inputs, clear the Input Conformer Collection parameter, then set it to the Restart Collection created by the original Gigadock job.
- Set the Cost Threshold parameter to the amount you estimate is needed to complete the run.
  
  Note
  
  If this threshold is exceeded in the new run, another Restart Collection will be created, and this procedure can be run again using that new Restart Collection.
Click “Start Job” to restart and complete the Gigadock Floe.

Note

The output of the restarted job will contain the output from the entire run, including the first run that stopped because it exceeded the threshold. There is no need to merge the results from the restarted job with the initial run.