It is often useful to be able to restart a job if it failed due to an intermittent error.
Only jobs which successfully reached the Provisioning stage are allowed to be restarted.
Jobs which failed during job creation cannot be restarted.
Only jobs which are currently in a terminal state (
SchedulingTimeout) are allowed to be restarted.
A running job or a job that is currently being created cannot be restarted.
engine job restart adaptive-strut Restarted job adaptive-strut engine job status adaptive-strut 2019-03-21T22:36:23: Cloning 2019-03-21T22:36:25: ParseEngineFile 2019-03-21T22:36:25: ValidateDataAccess 2019-03-21T22:36:25: ValidateInputDir 2019-03-21T22:36:25: CalculateResources 2019-03-21T22:36:25: PrepareEngineEnvironment 2019-03-21T22:36:25: BuildingDocker 2019-03-21T22:36:28: TaggingDocker 2019-03-21T22:36:28: PushingDocker 2019-03-21T22:36:29: SubmittingJob 2019-03-21T22:36:29: Provisioning 2019-03-21T22:43:20: Synchronizing 2019-03-21T22:43:29: Running 2019-03-22T23:26:08: Finished 2019-03-22T23:36:28: Restarted 2019-03-22T23:36:29: Provisioning 2019-03-22T23:43:20: Synchronizing 2019-03-22T23:43:29: Running 2019-03-23T00:12:08: Finished