9.6.7 Re-execution of a task
Function
Re-executes the specified task.
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/resubmit/ invoke
The following shows the structure of the request body.
{
"name" : "resubmit",
"href" : "http://host:port/Automation/version/objects/Tasks/id/actions/resubmit/invoke",
"method" : "POST",
"parameters" : [ {...} ]
}
The following table describes the objects that can be specified as parameters (member) in the schema of a request.
|
Function |
Resource name |
Number |
Description |
|---|---|---|---|
|
Schedule |
Schedule |
1 |
Execution schedule of the service |
|
List of property values |
PropertyValue |
0 to n |
Input property of the service |
The following describes the properties that can be specified.
- In the case of common settings:
-
Table 9‒42: In the case of common settings Resource name
Member name
Number
Schedule
name
1
Schedule
description
1
Schedule
scheduleType
1
PropertyValue
keyName
0 to n
PropertyValue
value
0 to n
- In the case of Now:
-
No property needs to be specified.
- In the case of Later:
-
Table 9‒43: In the case of Later Resource name
Member name
Number
Schedule
scheduledStartTime
1
- In the case of Recurring:
-
Table 9‒44: In the case of Recurring Resource name
Member name
Number
Schedule
recurrenceInterval
1
Schedule
recurrenceDayOfWeek
1
Schedule
recurrenceDayOfMonth
1
Schedule
recurrenceLastDayOfMonth
1
Schedule
recurrenceStartDate
1
Schedule
recurrenceTime
1
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 neither Completed nor Canceled. |
|
412 |
Precondition failed |
The server is not available. |
|
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 objects that can be output as affectedResources (member).
|
Output |
Resource name |
Number |
Description |
|---|---|---|---|
|
Link to the created schedule |
String |
1 |
Link to the created resource for schedule functionality (Schedules) |
|
Link to the created task |
String |
1 |
Link to the created resource for task functionality (Tasks) |
Usage example
In the following example, the API re-executes the task whose instanceID is 2026.
Request header:
POST /Automation/v1/objects/Tasks/2026/actions/resubmit/invoke HTTP/1.1
Host:10.196.184.238:22015
Accept:application/json
Accept-Language: ja
Content-Type: application/json
Content-Length: 821
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
User-Agent: useragent1
Response header:
HTTP/1.1 200 OK
Date: Mon, 14 Jul 2014 12:19:39 GMT
Server: Cosminexus HTTP Server
Access-Control-Expose-Headers: WWW-Authenticate
WWW-Authenticate: HSSO 5011884058b535482bf6bac7390956be5fc2122_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" : "d2a2284f-9a94-4be0-8813-e5f991762740",
"created" : "2014-07-14T05:19:40.089-0700",
"updated" : "2014-07-14T05:19:40.089-0700",
"completed" : "2014-07-14T05:19:40.089-0700",
"state" : "success",
"affectedResource" : [ "http://10.196.184.238:22015/Automation/v1/objects/Schedules/2060", "http://10.196.184.238:22015/Automation/v1/objects/Tasks/2063" ]
}