All Products
Search
Document Center

:CreateDagComplement

Last Updated:Jun 11, 2026

Calls CreateDagComplement to create a data backfill workflow.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

No authorization for this operation. If you encounter issues with this operation, contact technical support.

Request parameters

Parameter

Type

Required

Description

Example

ProjectEnv

string

Yes

The environment of the workspace, including PROD and DEV.

PROD

StartBizDate

string

Yes

The start business date of data backfill.

2020-05-20 00:00:00

Name

string

Yes

The name of the workflow.

xm_test

RootNodeId

integer

Yes

The ID of the start node for data backfill.

1234

IncludeNodeIds

string

Yes

The list of node IDs to include. If you backfill data for only one node, that node must be included in includeNodeIds.

74324,74325

ExcludeNodeIds

string

No

An optional parameter. The list of node IDs to exclude from data backfill.

1234

BizBeginTime

string

No

An optional parameter. The start time of the task. This parameter is required for hour-level scheduled tasks.

00:00:00

BizEndTime

string

No

An optional parameter. The end time of the task. This parameter is required for hour-level scheduled tasks.

23:00:00

Parallelism

boolean

Yes

Specifies whether the task can be executed concurrently.

false

EndBizDate

string

Yes

The end business date of data backfill.

2020-05-21 00:00:00

NodeParams

string

No

A JSON string. The key is the node ID, and the value is the actual parameter value.

{74324:"key1=val1 key2=val"}

Response elements

Element

Type

Description

Example

object

HttpStatusCode

integer

The HTTP status code.

200

RequestId

string

The request ID. The ID is used to locate logs and troubleshoot issues.

E6F0DBDD-5AD****

ErrorMessage

string

The error message.

The connection does not exist.

Success

boolean

Indicates whether the request was successful.

true

ErrorCode

string

The error code.

Invalid.Tenant.ConnectionNotExists

Data

array

The list of workflow IDs.

integer

The list of workflow IDs.

111

Examples

Success response

JSON format

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

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.