process studio - workflows - delay node management

  • Updated

Overview

A Delay node is configured to pause an execution for a specified period or until a specific condition is met. It serves as a delay between two nodes in a workflow template, allowing the execution to wait before continuing to the next step. The system calculates the delay based on the current system time and the defined configuration.

 

Prerequisites

  • A Workflow template must be created.   
  • A Starting rule must be configured on the canvas.   
  • An inbound path must be connected to the Delay node.

Required Permissions

  • Admin permissions with Workflow configuration access.

 

Configuration Steps

  1. Navigate to Control Center.
  2. Select Process Studio -> Workflows and edit or create a new workflow.
  3. Open the Delay Editor by clicking the node.
  4. Select the Delay Type. The following options can be configured:
  • After a set time: Pauses the execution for a linear set amount of time. Select the Time Units (Minutes, Hours, Days, Weeks, or Months) and enter the integer Duration.

  • On a specific date: Pauses the execution until the referenced date is reached. Select a date field from the Context or any related object for field mapping. Optionally, configure an Offset by selecting a time unit (Minutes, Hours, Days, Weeks, or Months) to add or subtract from the reference date.

  • At the next occurrence: Pauses the execution until a relative calendar target is met. Select the target, such as Wait Until Specific Weekday, Specific Day of Next Week, Wait Until Specific Day of the Month, or Specific Day Next Month, and define the corresponding day.

  1. Click SAVE. The setup is saved once all mandatory fields are completed and the Draft status is removed from the node.

 

Dependencies and Limitations

  • Delays only wait for moments in the future.
  • If the selected date field for an On a specific date delay is empty, the delay is skipped and the next step runs immediately.
  • If the resolved date is in the past, the delay is skipped.

 

Validation and Expected Results

Executions can be monitored from the global list located at Control Center -> Process Studio -> Workflows -> Running tab or within the contextual Workflows view of a specific Project or Lead record.

  • When an execution reaches the Delay node, it waits for the configured time before successfully following the outbound path.
  • Clicking the Delay node during an execution opens the sidebar, which displays a chronological activity feed grouped by date.
  • The feed records when the delay started, how the end time was calculated (including the field used, value, and offset), and when the workflow resumed.
  • Skipped delays are recorded as already elapsed within the feed.

 

Troubleshooting

  • Problem Description: An execution is in the Running status but appears stalled at a Delay node.  
  • Symptoms: The workflow has no recent activity and is waiting on a delay that has not elapsed.  
  • Possible Causes: The configured delay time either has not been reached or the offset calculation resulted in a future date.
  • Diagnostic Steps: Open the Delay sidebar within the execution view. Review the calculation breakdown to read the resolved end time.   
  • Resolution Steps: Wait for the elapsed time to pass or stop the execution manually if the delay configuration is incorrect.   
  • Validation: Confirm whether the workflow resumes after the resolved end time is reached.