Stopping a Graph (1.0.0)
Function
This API is used to stop a graph. After the graph is created, you can disable it if it is not used temporarily.
Instances of disabled graphs are not charged.
URI
- URI format
POST /v1.0/{project_id}/graphs/{graph_id}/action?action_id=stop - Parameter description
Table 1 URI parameter description Parameter
Mandatory
Type
Description
project_id
Yes
String
Project ID, which is used for resource isolation. For details, see Obtaining a Project ID.
graph_id
Yes
String
Graph ID
Request
- Request example
POST https://Endpoint/v1.0/{project_id}/graphs/{graph_id}/action?action_id=stop
Response
- Parameter description
Parameter
Mandatory
Type
Description
errorMessage
No
String
System prompt. If execution succeeds, this parameter may be left blank. If execution fails, this parameter is used to display the error message.
errorCode
No
String
System prompt. If execution succeeds, this parameter may be left blank. If execution fails, this parameter is used to display the error code.
job_id
No
String
ID of the graph stopping job. This parameter is left blank when the request fails.
NOTE:You can view the job execution status and obtain the return result by querying the job ID. For details, see Task Center APIs.
- Response example (successful request)
Http Status Code: 200 { "jobId": "ff8080816025a0a1016025a5a2700007" } - Response example (failed request)
Http Status Code: 400 { "errorCode": "GES.7001", "errorMessage": "The graph is not running." }
Return Value
- Normal
- Abnormal
Table 2 Return code for failed requests Return Value
Description
400 Bad Request
Request error.
401 Unauthorized
Authentication failed.
403 Forbidden
No operation permission.
404 Not Found
The requested resource was not found.
500 Internal Server Error
Internal service error.
503 Service Unavailable
Service unavailable.
Last Article: Creating a Graph (2.2.2)
Next Article: Starting a Graph (1.0.0)
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.