Task Query
최신 업데이트：2022-10-14 15:24:41
Fmgr task query
Description
This interface provides for querying the execution status of Fmgr tasks.
Note: The format of the notification content of the Fmgr task received by notifyURL is the same as the format of the response content of this interface.
Request Description
GET /fmgr/status?persistentId=<persistentId>
HOST: <MgrDomain>
Parameter Description
| Parameter | Required | Description |
|---|---|---|
| persistentId | Yes | Task process ID. |
Response Description
If the request is successful, a Jsonstring with the following content is returned:
{
"id": "<id string>",
"code": <code int>,
"desc": "<desc string>",
"separate": "<separate string>",
"items": [
{
"cmd": "<cmd string>",
"code": "<code string>",
"desc": "<desc string>",
"error": "<error string>",
"hash": "<hash string>",
"fsize": "<fsize int>",
"key": "<key string>",
"url": "<url string>"
"decompresslist": "<list string>"
}
]
}
| Field name | Type | Description |
|---|---|---|
| id | string | The task process ID, that is, the persistentId of the Fmgr interface response. |
| code | int | 1. If it is the information obtained by the query interface, it indicates the task status code: 0pending, 1processing, 3processing completed, 4notifying, 5notification failure, 6notification success; 2. If it is the information obtained by the notification interface, it indicates the notification status, 1which is notified separately , if there is a task processing, 2separate notification, if there is a task processing failure, 3it means the notification is successful. |
| desc | string | A detailed description corresponding to the status code. |
| separate | string | Separate notification option, which 0means one-time notification, 1means separate notification. |
| items | array | Status information for each operation. If the processing request includes multiple operations, items contain multiple pieces of information. |
| cmd | string | Operation commands (fops). |
| code | string | Processing result status code, 0pending, 1processing, 2processing failure, 3processing success, 4processing success notification, 5processing success notification failure, 6processing success notification success, 18processing failure notification, 19processing failure notification failure, 20processing failure notification success, other ( For specific circumstances, please contact cloud storage staff). Note: The deletion of m3u8 files using the “Delete m3u8 files” interface fails, and some TSs may have been deleted. If you need to delete them completely, please initiate the m3u8 associated deletion operation again. |
| desc | string | A detailed description corresponding to the status code. |
| error | string | If processing failed, this field lists the specific reason. |
| fsize | int | The processed file size. Note: If deleting tasks by prefix, this field is empty. |
| hash | string | The value of the processing result hash. Note: If deleting tasks by prefix, this field is empty. |
| key | string | The value of the processing result key. Note: If the task is to be deleted by prefix, this field is the specified output; if no output is specified, this field is empty. |
| url | string | The access path to the resource. Note: If the task is to be deleted by prefix, this field is the specified output access URL; if no output is specified, this field is empty. |
| decompresslist | string | List file automatically generated after decompression.* Note: If there is no decompression operation, this field is empty.* |
If the request fails, a Jsonstring with the following content is returned:
{
"code":"<httpCode int>",
"message":"<errMsg string>"
}
| Field name | Required | Description |
|---|---|---|
| code | Yes | HTTP request response code, see HTTP response status code |
| message | Yes | A message indicating that the request failed. |
Example
curl -v http://mgrDomain/fmgr/status?persistentId=ff80808149deceff014a7090b6700000
이 문서의 내용이 도움이 되었습니까?
예
아니오