All Products
Search
Document Center

SchedulerX:ListWorkflowInstance

Last Updated:Dec 10, 2024

Queries the execution history of a workflow. You can call this operation only in the professional edition.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

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 Resources is 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.
OperationAccess levelResource typeCondition keyAssociated operation
edas:ReadSchedulerxWorkflowQueryget
*All Resources
*
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
RegionIdstringYes

The region ID.

cn-hangzhou
NamespacestringYes

The namespace ID. You can obtain the namespace ID on the Namespace page in the SchedulerX console.

adcfc35d-e2fe-4fe9-bbaa-20e90ffc****
NamespaceSourcestringNo

The source of the namespace. This parameter is required only for a special third party.

schedulerx
GroupIdstringYes

The application group ID. You can obtain the ID on the Application Management page in the SchedulerX console.

testSchedulerx.defaultGroup
WorkflowIdstringYes

The workflow ID.

123

Response parameters

ParameterTypeDescriptionExample
object

The response schema.

RequestIdstring

The request ID.

39090022-1F3B-4797-8518-6B61095F1AF0
Codeinteger

The HTTP status code.

200
Successboolean

Indicates whether the request was successful. Valid values:

  • true
  • false
true
Messagestring

The returned error message.

workflowId=xxx is not existed
Dataobject

The information about workflow instances.

WfInstanceInfosarray<object>

The workflow instances.

WfInstanceInfosobject

The data structure of the workflow instance.

WfInstanceIdlong

The workflow instance ID.

123456
WorkflowIdlong

The workflow ID.

123
Statusinteger

The state of the workflow instance. Valid values:

  • 1: pending
  • 2: preparing
  • 3: running
  • 4: successful
  • 5: failed
5
StartTimestring

The time when the workflow instance started to run.

2023-01-03 18:00:01
EndTimestring

The time when the workflow instance stopped running.

2023-01-03 18:00:21
ScheduleTimestring

The time when the workflow instance was scheduled to run.

2023-01-03 18:00:00
DataTimestring

The data timestamp of the workflow instance.

2023-01-03 18:00:00

Examples

Sample success responses

JSONformat

{
  "RequestId": "39090022-1F3B-4797-8518-6B61095F1AF0",
  "Code": 200,
  "Success": true,
  "Message": "workflowId=xxx is not existed",
  "Data": {
    "WfInstanceInfos": [
      {
        "WfInstanceId": 123456,
        "WorkflowId": 123,
        "Status": 5,
        "StartTime": "2023-01-03 18:00:01",
        "EndTime": "2023-01-03 18:00:21",
        "ScheduleTime": "2023-01-03 18:00:00",
        "DataTime": "2023-01-03 18:00:00"
      }
    ]
  }
}

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-10-18The response structure of the API has changedView Change Details