Call the ResumeLogstashTask to resume the change interruption task for the instance. After restoration, the instance enters the activating state.


OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. You can use OpenAPI Explorer to search for API operations, call API operations, and dynamically generate SDK sample code.

Request header

This operation uses only common request headers. For more information, see Common parameters.

Request syntax

POST /openapi/logstashes/[InstanceId]/actions/resume HTTPS|HTTP

Request parameters

Parameter Type Required Example Description
InstanceId String Yes ls-cn-4591f1y6****

The ID of the instance.

clientToken String No 5A2CFF0E-5718-45B5-9D4D-70B3FF****

A unique token generated by the client to guarantee the idempotency of the request. The value of this parameter is generated by the client and is unique among different requests. The maximum length is 64 ASCII characters.

Response parameters

Parameter Type Example Description
Code String InstanceNotFound

The error code. This parameter is not returned if you call the operation normally.

Message String The specified cluster does not exist. Check the cluster status and try again.

The error message. This parameter is not returned if you call the operation normally.

RequestId String 0FA05123-745C-42FD-A69B-AFF48EF9****

The ID of the request.

Result Boolean true

Returned results:

  • true: The restore task is successful.
  • false: The restore task failed.


Sample requests

POST /openapi/logstashes/ls-cn-4591f1y6 ****/actions/resume HTTP/1.1 
common request header

Sample success responses

JSON Syntax

    "Result": true,
    "RequestId": "0FA05123-745C-42FD-A69B-AFF48EF9****"

Error codes

HttpCode Error code Error message Description
400 InstanceNotFound The instanceId provided does not exist. The error message returned because the instance cannot be found. Check the status of the instance.

For a list of error codes, visit the API Error Center.