9.6.11 Retry from the step after the failed step
Function
Specifies a task, and retries the task from the step after the failed step.
Execution permissions
Admin role, Develop role, Modify role, Submit role
API version
v1
Request format
POST http://host:port/Automation/version/objects/Tasks/id/actions/rerunStepStart/invoke
The following shows the structure of the request body.
{
"name" : "rerunStepStart",
"href" : "http://host:port/Automation/version/objects/Tasks/id/actions/rerunStepStart/invoke",
"method" : "POST",
"parameters" : null
}
Status code
The following table describes the various status codes that can be returned as the response to a request.
|
Status code |
Message |
Description |
|---|---|---|
|
200 |
Created |
Processing has been successfully completed. |
|
400 |
Bad Request |
The argument is invalid. |
|
401 |
Unauthorized |
The user does not have login permission. |
|
404 |
Not found |
The permission is invalid, or the resource does not exist. |
|
409 |
Conflict |
The status of the task is not Failed. |
|
412 |
Precondition failed |
The server is not running. |
|
500 |
Server-side error |
A server processing error occurred. |
Response schema
The following shows the structure of the response body for a request.
{
"instanceId" : "instance-id",
"created" : "created-date-and-time",
"updated" : "updated-date-and-time",
"completed" : "completed-date-and-time",
"state" : "state",
"affectedResources" : [ {...} ]
}
The following table describes the object that can be output as affectedResources (member).
|
Output |
Resource name |
Number |
Description |
|---|---|---|---|
|
Link to the affected task |
String |
1 |
Link to the updated resource for task functionality (Tasks) |
Usage example
In the following example, the API retries the task whose instanceID is 2052 from the step after the failed step.
Request header:
POST /Automation/v1/objects/Tasks/2052/actions/rerunStepStart/invoke HTTP/1.1
Host:10.196.184.238:22015
Accept:application/json
Accept-Language: ja
Content-Type: application/json
Content-Length: 184
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
User-Agent: useragent1
Response header:
HTTP/1.1 200 OK
Date: Mon, 14 Jul 2014 11:58:17 GMT
Server: Cosminexus HTTP Server
Access-Control-Expose-Headers: WWW-Authenticate
WWW-Authenticate: HSSO 4c41b543aa586cdc7eda448abadac3ff6268be_V0300
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, DELETE, PUT, HEAD, OPTIONS
Access-Control-Allow-Credentials: true
Cache-Control: no-cache
Transfer-Encoding: chunked
Content-Type: application/json
Response body:
{
"instanceID" : "cabe6176-498a-44ed-9691-5d270213f9b7",
"created" : "2014-07-14T04:58:17.957-0700",
"updated" : "2014-07-14T04:58:17.957-0700",
"completed" : "2014-07-14T04:58:17.957-0700",
"state" : "success",
"affectedResource" : [ "http://10.196.184.238:22015/Automation/v1/objects/Tasks/2052" ]
}