2.7.17 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" : [ ] }
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 |
OK |
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" : [ {...} ] "result" : [ {...} ], "resultType" : "result-type" }
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 5381 from the step after the failed step.
Request header: POST /Automation/v1/objects/Tasks/5381/actions/rerunStepStart/invoke HTTP/1.1 Host: 192.168.146.132:22015 User-Agent: curl/7.36.0 Accept: application/json Content-Type: application/json Content-Length: 185 Authorization: Basic c3lzdGVtOm1hbmFnZXI= Accept-Language: ja Response header: HTTP/1.1 200 OK Date: Fri, 07 Aug 2015 10:29:33 GMT Server: Cosminexus HTTP Server Access-Control-Expose-Headers: WWW-Authenticate WWW-Authenticate: HSSO c19a775746fbd61d1efd3658d2b4eacadcfe435_Vlo8Y30JBWoKHUYTEXAMXx5iHgQ=_V0810 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" : "852af753-989f-4797-a7dc-50faaf07b896", "created" : "2015-08-07T19:29:33.562+09:00", "updated" : "2015-08-07T19:29:33.562+09:00", "completed" : "2015-08-07T19:29:33.562+09:00", "state" : "success", "affectedResource" : [ "http://192.168.146.132:22015/Automation/v1/objects/Tasks/5381" ], "result" : [ ] }