Creates a workflow to backfill data.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters

Parameter Type Required Example Description
Action String Yes RunCycleDagNodes

The operation that you want to perform.

EndBizDate String Yes 2020-05-21 00:00:00

The date and time at which data is no longer backfilled. Specify this parameter in the yyyy-MM-dd 00:00:00 format.

IncludeNodeIds String Yes 74324,74325

The ID of the node for which you want to backfill data. If you want to backfill data for multiple nodes, separate the IDs of the nodes with commas (,). You can call the ListNodes operation to query the node IDs.

Name String Yes xm_test

The name of the workflow.

Parallelism Boolean Yes false

Specifies whether data can be backfilled for multiple nodes at the same time.

ProjectEnv String Yes PROD

The environment of the workspace. Valid values: PROD and DEV. The value PROD indicates the production environment. The value DEV indicates the development environment.

RegionId String Yes cn-shanghai

The region ID. For example, the ID of the China (Shanghai) region is cn-shanghai, and that of the China (Zhangjiakou) region is cn-zhangjiakou. The system automatically determines the value of this parameter based on the endpoint used to call the operation.

RootNodeId Long Yes 1234

The ID of the node for which data is first backfilled. You can call the ListNodes operation to query the ID.

StartBizDate String Yes 2020-05-20 00:00:00

The date and time at which data starts to be backfilled. Specify this parameter in the yyyy-MM-dd 00:00:00 format.

ExcludeNodeIds String No 1234,123465

The IDs of the nodes for which no data needs to be backfilled. The system generates dry-run instances for all these nodes. After these dry-run instances are scheduled, the statuses of these instances are directly set to successful, but the script is not run.

BizBeginTime String No 00:00:00

The time when the node was run. This parameter is required only for auto triggered nodes that are scheduled by hour. Specify this parameter in the HH:mm:ss format. Valid values: 00:00:00 to 23:59:59.

BizEndTime String No 01:00:00

The time when the node was successfully run. This parameter is required only for auto triggered nodes that are scheduled by hour. Specify this parameter in the HH:mm:ss format. Valid values: 00:00:00 to 23:59:59.

NodeParams String No {74324:"key1=val1 key2=val"}

The parameters that need to be configured for the node. Set this parameter to a JSON string. The key represents the node ID, and the value represents the actual values of the parameters.

Response parameters

Parameter Type Example Description
Data List 111

The IDs of the nodes in the workflow.

ErrorCode String Invalid.Tenant.ConnectionNotExists

The error code returned.

ErrorMessage String The connection does not exist.

The error message returned.

HttpStatusCode Integer 200

The HTTP status code returned.

RequestId String >E6F0DBDD-5AD****

The ID of the request. You can use the ID to locate logs and troubleshoot issues.

Success Boolean true

Indicates whether the request is successful.

Examples

Sample requests

http(s)://[Endpoint]/?Action=RunCycleDagNodes
&EndBizDate=2020-05-21 00:00:00
&IncludeNodeIds=74324,74325
&Name=xm_test
&Parallelism=false
&ProjectEnv=PROD
&RegionId=cn-shanghai
&RootNodeId=1234
&StartBizDate=2020-05-20 00:00:00
&<Common request parameters>

Sample success responses

XML format

<RequestId>E6F0DBDD-5AD****</RequestId>
<HttpStatusCode>200</HttpStatusCode>
<Data>111</Data>
<ErrorCode>Invalid.Tenant.ConnectionNotExists</ErrorCode>
<ErrorMessage>The connection does not exist.</ErrorMessage>
<Success>true</Success>

JSON format

{
    "RequestId": "E6F0DBDD-5AD****",
    "HttpStatusCode": 200,
    "Data": 111,
    "ErrorCode": "Invalid.Tenant.ConnectionNotExists",
    "ErrorMessage": "The connection does not exist.",
    "Success": true
}

Error codes

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