SharePoint Online - Wait for event in list item
Use the SharePoint Online - Wait for event in list item action A tool for building the processes, logic, and direction within workflows. Actions are the steps the workflow performs to complete a process. to pause a workflow until a selected event occurs in the specified SharePoint Online list. The workflow pauses and resumes only when the event occurs. You can add conditions to specify a particular item or field that has to be updated or added for the workflow to resume.
For more information about the SharePoint Online connector, go to SharePoint Online.
Configure the SharePoint Online - Wait for event in list item action
-
Add the action to the designer canvas and open the action configuration panel. For more information, see Add an action to the workflow.
- Select the Event that has to happen for the workflow to resume.
-
Select a SharePoint Online Connection. If you do not have a connection, see Add a connection.
-
Type a SharePoint site URL.
Example:https://domain.sharepoint.com/sites/hr
-
Click Retrieve lists to retrieve the lists from the SharePoint site.
- Select the List name.
Note: Only the connections created with the List and libraries authentication method are available in the drop-down. For more information about authentication methods for SharePoint Online connections, see Authentication methods for SharePoint Online connections.
SharePoint Online - Wait for event in list item action fields and settings
Best practices when using SharePoint Online - Wait for event in list item action in parallel branches
When using the SharePoint Online - Wait for event in list item action in parallel branches, carefully design the workflow to ensure efficient event handling and prevent unnecessary event subscriptions.
Avoid placing multiple wait actions for the same SharePoint list item inside parallel branches.
Instead, use a single wait action with combined conditions using nested OR logic. This allows the workflow to respond to multiple possible outcomes within a single action instead of splitting the logic across multiple branches.
Impact of multiple wait actions in parallel branches
Each wait action creates its own SharePoint event subscription.
When multiple wait actions are used within parallel branches, separate event subscriptions remain active until the workflow completes, even after one branch condition has already been met.
Over time, this can result in too many active subscriptions and may reach SharePoint event subscription limits or Nintex event evaluation limits. For more information, see Maximum number of event evaluations.
Recommended configuration
-
To handle multiple possible outcomes for the same list item, use one SharePoint Online - Wait for event in list item action.
-
Configure all required conditions within the same action using OR logic in the Condition builder. For example, (FieldA = Pass) OR (FieldA = Fail) OR (Status changes).
Where required, you can apply AND conditions to further refine the event criteria.