Queries media workflow execution instances.
Operation description
- You can call this operation to query a maximum of 10 media workflow execution instances at a time.
- Before you call this operation, make sure that the workflow pipeline is enabled. Otherwise, the workflow may not run as expected. For example, the following exceptions may occur: the workflow node is invalid and jobs created in the workflow cannot be executed.
QPS limit
You can call this operation up to 100 times per second per account. Requests that exceed this limit are dropped and you will experience service interruptions. We recommend that you take note of this limit when you call this operation. For more information, see QPS limit.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| mts:QueryMediaWorkflowExecutionList | get |
|
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| RunIds | string | Yes | The IDs of the media workflow execution instances. To obtain the instance ID, log on to the ApsaraVideo Media Processing (MPS) console and choose Workflows > Execution Instances in the left-side navigation pane. Separate multiple IDs with commas (,). You can query a maximum of 10 media workflow execution instances at a time. | 48e33690ac19445488c706924321**** |
Response parameters
Examples
Sample success responses
JSONformat
{
"NonExistRunIds": {
"RunId": [
"null"
]
},
"MediaWorkflowExecutionList": {
"MediaWorkflowExecution": [
{
"CreationTime": "016-04-01T06:53:43Z",
"MediaWorkflowId": "93ab850b4f6f44eab54b6e91****81d4",
"State": "Completed",
"ActivityList": {
"Activity": [
{
"EndTime": "2016-04-01T06:53:44Z",
"Type": "Start",
"StartTime": "2016-04-01T06:53:44Z",
"State": "Running",
"JobId": "2376030d9d0849399cd20e20f4f3****",
"Code": "InvalidParameter.ResourceContentBad",
"Message": "The resource operated InputFile is bad",
"Name": "Start",
"MNSMessageResult": {
"MessageId": "4f3bc83233de4e2f81c7dade443e****",
"ErrorMessage": "MessageConfigEmpty",
"ErrorCode": "The Topic/Queue config is empty, not send message"
}
}
]
},
"Name": "example-mediaworkflow-****",
"Input": {
"UserData": "example data ****",
"InputFile": {
"Object": "example-mediaWorkflow-****/example-object-****/example.mp4",
"Location": "mps-cn-shanghai",
"Bucket": "example-bucket-****"
}
},
"MediaId": "512046582a924698a41e0f8b0d2b****",
"RunId": "48e33690ac19445488c706924321****"
}
]
},
"RequestId": "D1D5C080-8E2F-5030-8AB4-13092F17631B"
}Error codes
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|