Updated on 2024-08-14 GMT+08:00

Step

A step is the smallest unit of a workflow. In a DAG, a step is also a phase. Different types of steps have different service abilities. The main parts of a step are as follows.

Table 1 Step

Parameter

Description

Mandatory

Data Type

name

Phase name. The name can contain a maximum of 64 characters, including only letters, digits, underscores (_), and hyphens (-), and must start with a letter.

Yes

str

title

Title of a phase, which is displayed in the DAG. If this parameter is not configured, the name is displayed by default.

No

str

step_type

Type of a phase, which determines the function of the phase

Yes

enum

inputs

Inputs of a phase

No

AbstractInput or list[AbstractInput]

outputs

Outputs of a phase

No

AbstractOutput or list[AbstractOutput]

properties

Node properties

No

dict

policy

Phase execution policy, which includes the phase scheduling interval, the phase execution timeout interval, and the option to skip phase execution

No

StepPolicy

depend_steps

List of dependency phases. This parameter determines the DAG structure and phase execution sequence.

No

Step or list[Step]

Table 2 StepPolicy

Parameter

Description

Mandatory

Data Type

poll_interval_seconds

Phase scheduling interval. The default value is 1 second.

Yes

str

max_execution_minutes

Phase execution timeout interval. The default value is 10080 minutes, that is, 7 days.

Yes

str

skip_conditions

Conditions that determine whether a phase is skipped

No

Condition or condition list

Step is a superclass of a phase. It has a conceptual role and is not used directly by you. Different types of phase are created based on functions, including CreateDatasetStep, LabelingStep, DatasetImportStep, ReleaseDatasetStep, JobStep, ModelStep, ServiceStep and ConditionStep. For details, see Phase Type.