All Products
Search
Document Center

DataWorks:CreateDagComplement

Last Updated:Jul 31, 2026

Creates a data backfill workflow by calling CreateDagComplement.

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. Valid values:

  • PROD: production environment.

  • DEV: development environment.

Valid values:

  • PROD :

    Production environment.

  • DEV :

    Development environment.

PROD

StartBizDate

string

Yes

The start business date for the data backfill.

Format: yyyy-MM-dd HH:mm:ss. Example: 2020-05-20 00:00:00.

2020-05-20 00:00:00

Name

string

Yes

The name of the workflow.

xm_test

RootNodeId

integer

Yes

The ID of the root node for the data backfill.

1234

IncludeNodeIds

string

Yes

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

74324,74325

ExcludeNodeIds

string

No

Optional. The list of node IDs to exclude from the data backfill.

1234

BizBeginTime

string

No

Optional. The start time of the task. This parameter is required for hourly scheduled tasks.

Format: HH:mm:ss. Example: 00:00:00.

00:00:00

BizEndTime

string

No

Optional. The end time of the task. This parameter is required for hourly scheduled tasks.

Format: HH:mm:ss. Example: 23:00:00.

23:00:00

Parallelism

boolean

Yes

Specifies whether tasks can execute concurrently.

false

EndBizDate

string

Yes

The end business date for the data backfill.

Format: yyyy-MM-dd HH:mm:ss. Example: 2020-05-21 00:00:00.

2020-05-21 00:00:00

NodeParams

string

No

A JSON string in which 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. Used to locate logs and troubleshoot issues.

E6F0DBDD-5AD****

ErrorMessage

string

The error message.

The connection does not exist.

Success

boolean

Indicates whether the call 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.