Published at: 2026-09-17

Configure business process wait nodes

Configure a Wait Node that pauses a process, delays routing for a fixed duration, or continues after specified conditions are met.

Overview

A Wait Node pauses progress in a Business Process. When the Process reaches the Wait Node, the System uses the configured wait mode to decide when to continue.

Wait Nodes Support two wait modes:

Wait mode	Description	Use case
Condition Wait	The System keeps waiting until the Configured condition is met, and then continues routing	Wait for an External Status change, Field Update, or third-party System callback
Delay Wait	The System waits for the specified duration, and then continues automatically	Send a Reminder after a fixed Time, delay an Automatic action, or reserve response Processing Time for the Handler

In the process canvas, you can select Wait Node, drag it to the canvas, and Configure the Node Name, Business Description, Business Object, task data, wait mode, and actions in the right-side Node Settings panel.

The core settings include:

Which Business Object the current Wait Node applies to.
Which Business Data record the wait task applies to.
Which wait mode to use: Condition Wait or Delay Wait.
The wait condition or wait duration.
The Automatic actions related to the Wait Node.
Whether the Process enters the correct next Node after waiting ends.

Before you begin

The Business Process is created, and you are on the process canvas configuration page.
You have Confirmed where the Process must pause.
You have Confirmed the wait mode: wait by condition or delay for a fixed duration.
If you use Condition Wait, Confirm the Field, Status, or Business Data Source for the condition.
If you use Delay Wait, Confirm the wait duration and Unit.
If actions must run after the wait ends, Confirm the action Type and Execution Order.

Configure Node Settings

Select the Wait Node on the process canvas, and then Configure the following items on the right-side Node Settings tab.

Configuration item	Description
Node Name	The Name of the current Wait Node on the canvas and in Process records. Use a specific target, such as “Wait for customer receipt” or “Wait for evaluation result”
Business Description	Describes why this Wait Node is used. This helps admins understand the wait reason. The limit is 500 characters
Which Object this Business Activity applies to	Select the main Business Object for the current Wait Node, such as Work Order
Which Work Order to execute the task on	Select the data Source that the Node actually waits on, such as Related Data/Work Order
Wait mode	Select Condition Wait or Delay Wait
What this task needs to do	Configure actions to run in the Wait Node. Click Add to add actions, and drag actions to adjust the order

Configure the Business Object and task data

A Wait Node must first identify the Business Object that it waits for and the actual record that it is associated with.

In Node Name, enter a recognizable Wait Node Name.
In Business Description, describe why the Process must wait here.
In Which Object this Business Activity applies to, select the Object related to this Business Activity, such as Work Order.
In Which Work Order to execute the task on, select the data Source for the wait, such as Related Data/Work Order.

The Business Object determines the Data Range available to wait conditions. The task data determines which record the System checks or updates when it evaluates conditions or runs actions.

Configure the wait mode

In Wait mode, select the wait Type for the current Node.

Condition Wait

Condition Wait waits until Business Data meets a specified condition. After the Process reaches the Wait Node, the System checks the condition continuously. When the condition is met, the Process continues.

Configuration steps:

Add a Wait Node and select it.
In Wait mode, select Condition Wait.
Configure the wait condition, such as a Field value, Status, Business result, or another condition that the System can evaluate.
If the page Supports a check interval or timeout rule, set it according to business requirements.
Connect the next Node.
Click Save as Draft or Save and Submit.

Condition Wait is suitable for these scenarios:

Wait for the Account to Confirm receipt.
Wait for the Service Evaluation result to be returned.
Wait for an External System to synchronize Status.
Wait for the Work Order Status to change to a specified value.
Wait for a Field to be filled in or Updated.

Delay Wait

Delay Wait makes the Process wait for a fixed duration before it continues. After the Process reaches the Wait Node, the System does not enter the next Node immediately. It continues after the wait duration ends.

Configuration steps:

Add a Wait Node and select it.
In Wait mode, select Delay Wait.
Set the wait duration and Time Unit.
Connect the next Node.
Click Save as Draft or Save and Submit.

Delay Wait is suitable for these scenarios:

Wait for a period after Service completion before starting a follow-up visit.
Delay the next step after a notification is sent.
Reserve Processing Time for the Account or Service Provider.
Delay an Automatic Node or subsequent Business Activity.

[!NOTE] Condition Wait is suitable for External Status or Business Data changes. Delay Wait is suitable when the Process must continue after a fixed Time.

Configure Wait Node actions

You can Add actions in What this task needs to do. The screenshot shows that this area Supports Add and lets you drag actions to adjust their Execution Order.

Common actions include Field changes, notifications, Initiate Business Process, Execute APL code, Lock or Unlock data, tasks, schedules, variable assignment, and Conversion Rules. Use the action area as the Action Configuration for this Node. The available actions depend on the actual page.

Configuration recommendations:

If you need to record Status At Start Time, Configure a Field change first. For example, Update the Work Order Status to “Waiting”.
If you need to remind related Personnel during the wait, Configure SMS, Email, or CRM Reminders.
If subsequent System handling must run after the wait ends, combine the Wait Node with an Automatic Node or post-completion actions.
If multiple actions depend on each other, arrange them in the business Execution Order.

Common validation and error handling

If the Wait Node configuration is incomplete, the page may show an error. For example, 1 error found at the top of the screenshot usually means that required items are missing or Node connections are incomplete.

Common Inspection Items include:

Whether Node Name is filled in.
Whether Which Object this Business Activity applies to is selected.
Whether Which Work Order to execute the task on is selected.
Whether Wait mode is selected.
Whether the complete wait condition is Configured for Condition Wait.
Whether the wait duration is Configured for Delay Wait.
Whether the Wait Node is connected to the next Node.

Before you Save or Submit, fix each item according to the page Notice.

Configuration recommendations

Use a Wait Node Name that directly describes the wait target, such as “Wait for customer receipt” or “Wait for service evaluation callback”.
For Condition Wait, choose stable, clear, and evaluable Fields or Status values. Avoid conditions that might never be met.
For Delay Wait, set a reasonable duration to avoid unnecessary Process idle Time.
If the wait result depends on an External System, also Confirm its callback mechanism and Abnormal handling.
Keep follow-up connections clear, and make sure the Process enters the correct Node after the wait ends.
If notifications or Status markers are needed during the wait, combine Node actions, Automatic Nodes, or post-completion actions.

Expected result and validation

Start a test Business Process.
Let the Process run to the Wait Node.
Check whether the Process stays at the Wait Node.
If Condition Wait is Configured, modify test data so that the condition is met, and check whether the Process continues.
If Delay Wait is Configured, wait for the specified duration and check whether the Process continues automatically.
Check whether the actions Configured in the Wait Node run as expected.
View the Process Log and Confirm records for wait start, wait end, and subsequent routing.