Performing Operations on a Script Service Ticket
Function
This API is used to perform operations on a script ticket.
The operation types include cancelling instances, skipping a batch, cancelling an entire service ticket, suspending an entire service ticket, and continuing a service ticket.
URI
PUT /v1/job/script/orders/{execute_uuid}/operation
Parameter | Mandatory | Type | Description |
|---|---|---|---|
execute_uuid | Yes | String | Execution ID of a script service ticket, which is obtained from the response bodies of executeJobScript and ListJobScriptOrders. Minimum length: 1 character Maximum length: 26 characters |
Request Parameters
Parameter | Mandatory | Type | Description |
|---|---|---|---|
batch_index | No | Integer | Applicable to batch operations Minimum value: 1 Maximum value: 20 |
instance_id | No | Long | Applicable to instance operations. Minimum value: 1 Maximum value: 9223372036854775807 |
operation_type | Yes | String | Operation type. The options are as follows: CANCEL_INSTANCE: canceling an instance; SKIP_BATCH: skipping a batch; CANCEL_ORDER: canceling an entire service ticket; PAUSE_ORDER: suspending an entire service ticket; CONTINUE_ORDER: continuing an entire service ticket. The value can be:
|
Response Parameters
None
Request Example
{
"batch_index" : "1",
"instance_id" : 383,
"operation_type" : "RETRY_INSTANCE"
} Response Example
None
Status Code
Status Code | Description |
|---|---|
200 | execution_uuid |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.

