Topology execution events

When editing a topology graph, click a target node and then click the icon next to the node to add an execution event.

Beta events

This event is valid only in the BETA trigger mode. When a task node has a Beta event, the topology automatically aborts after the node runs and waits for manual confirmation. Subsequent nodes run only after this confirmation is provided and other execution conditions are met.

When a topology execution is aborted because of a Beta event, its execution status remains 'Running'.

Loop events

A node with a loop event enters a loop when it starts to run. After each loop, the node updates a custom parameter and checks whether the exit condition is met. If the condition is met, the loop ends and the topology task continues. Otherwise, the node continues to loop until the condition is met.

Loop events require the following parameters:

• Loop exit condition: A conditional expression for the custom parameter.

• Loop interval: The interval for the loop event, specified in hours or minutes.

• Maximum loop count: The maximum number of executions for the loop event. If this count is exceeded, the task stops. The value can range from 1 to 20, and the default is 20.

Wait events

A task node with a wait event is automatically delayed and will only execute when a specified wait condition is met.

Wait events support the following four wait patterns:

• Wait immediately: The task flow enters a waiting state as soon as it reaches this event.

• Wait until a specific time: Delays the task to run at a specific time on the same day or the next day. The time is in the HH:mm 24-hour format.

• Wait for an interval: Delays the task to run after a specified interval. The interval can be set in hours or minutes.

• Conditional wait: Determines whether to wait based on parameters passed from the context.

You can skip a task node that is in a waiting state. In the scheduling records, click the skip button next to the node to run the subsequent tasks.