The Workflows feature is a fully managed workflow scheduling feature that helps schedule batch deployments on a GUI in an efficient manner. You can use the Workflows feature to build a data warehouse and implement integration of development, scheduling, deployment, and O&M in the Realtime Compute for Apache Flink console.
The Workflows feature is in public preview. The service level agreement (SLA) is not guaranteed in the public preview phase. For more information, see Realtime Compute for Apache Flink SLA. If you have questions when you use the Workflows feature, submit a ticket.
The Workflows feature is supported only in the China (Shanghai), China (Hangzhou), China (Beijing), China (Shenzhen), China (Zhangjiakou), and Singapore regions.
Features
Visualized management: allows you to create or manage workflows in a visualized manner.
Scheduling: supports manual scheduling and periodic scheduling.
Scheduled management: allows you to use cron expressions to specify complex scheduling rules.
Queue management: allows you to configure different queues for workflows and tasks.
Terms
Workflow
A workflow is a directed acyclic graph (DAG) that you can create based on the Workflows feature. You can create a workflow and configure tasks and scheduling policies in the workflow to run the tasks at specified points in time.
Task
A task runs in a workflow. Each task must be associated with a deployment.
Workflow instance
A workflow instance is generated each time a workflow runs.
Task instance
Task instances are generated by tasks each time a workflow runs.
Dependency
A dependency indicates the relationship between tasks. For example, if Task A and Task B are displayed as Task A -> Task B on the task editing page, Task A is the upstream task on which Task B depends. Task B can run only after the conditions that are specified for Task B are met and Task A is complete.
Workflow version
A workflow version is generated for a workflow each time you modify the workflow. For example, if you add or remove a task or change the dependency between tasks, a new workflow version is generated.
Procedure
