---
sourceDocument: Yokohama Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/build-workflows

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Start with delay input properties

# Start with delay input properties {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Start with delay input properties

The "Start with delay" input allows you to specify a waiting period before executing an activity or stage in a playbook, even after the start conditions are met.
This feature helps users provide a pause for manual actions or wait until a specific date and time before proceeding in automated workflows.
Show full answer Show less  

## Roles and Availability

This input is available for all stages and common activities except the Placeholder activity. Users assigned to the roles **admin** , **playbook.admin** , **pdauthor** , or **pdcontentauthor** can configure these delay properties.

## Input Properties and Configuration

To enable and configure the delay, open the properties panel of an activity or stage, access additional options, and enable the "Start with delay" setting. The main configurable properties include:

* **Duration Type:** Defines the basis of the delay with three options:
  * **Explicit Duration:** Wait for a fixed time period (e.g., 5 minutes).
  * **Relative Duration:** Wait for a time period relative to a selected date/time or duration data pill (e.g., 5 minutes after playbook start).
  * **Percentage Duration:** Wait for a percentage of the time between the activity/stage start and a specified end time (values from 0 to 100%).
* **Wait for Template Value:** Allows manual entry of duration or selection of a Duration data pill. For relative durations, specify wait times before or after a certain date/time. Maximum wait is 999 hours. Note that actual delays may vary due to system processing times.
* **Wait for Percentage:** When using Percentage Duration, specify the percentage of time to wait relative to a defined end date or date/time data pill. Past end dates default the wait duration to zero.
* **During the following schedule:** Optionally assign a schedule (from Reference.Schedule \[cmnschedule\]) to calculate the end date within business hours or operational times. If left blank, no schedule is applied.

## Practical Benefits for ServiceNow Customers

* Enables precise control over timing in playbook executions, allowing for deliberate pauses before activities or stages begin.
* Supports diverse timing strategies---fixed delays, relative waits based on dynamic data, or proportional timing based on overall durations.
* Facilitates alignment with business hours and operational schedules to ensure delays respect organizational workflows.
* Empowers users to design automated playbooks that incorporate manual intervention windows or timed waits for compliance and operational efficiency.

## Related Configuration and Concepts

This feature integrates with activity definitions, automation assets, and playbook activity state mapping. It supports use cases involving optional activities, decision activities, parallel branches, and questionnaires. For further setup, customers can refer to adding and configuring stages, activities, dynamic inputs, and scheduling within playbooks.  
Specify a duration of time to wait before running an activity or a stage whose start rule and conditions have been met. Give users time to act during automated playbooks. Give users time to wait for a specific date and time to complete actions.

## Roles and availability {#start-with-delay-properties__section_pwq_rb5_kcb}

This input is available for all stages and common activities, except for the Placeholder activity. Users with the admin, playbook.admin, pd_author, or pd_content_author can configure the properties of this input.

## Input properties {#start-with-delay-properties__section_yb4_zq3_plb}

Open the activity or stage properties panel, show additional options, and enable the Start with delay option to configure the following input properties. {#start-with-delay-properties__table_ajt_sr3_plb__entry__3}

| Input | Type | Description |
|-|-|-|
| Duration Type | Choice | Option to specify how long of duration to wait. Options include * Explicit Duration: Wait for a specific time period, such as 5 minutes. * Relative Duration: Wait for a specific time period from a selected Duration data pill or date/time value, such as 5 minutes after the playbook starts. * Percentage Duration: Wait for a specific percentage of a time period between the start of the activity or stage and a specified end time, such as 50%. Note: The percentage value must be from 0 through 100 only. {#start-with-delay-properties__ul_ixy_42f_ffc} |
| Wait for | Template Value | Option to set a duration value manually or to select a Duration data pill from the data pill picker (![Data pill picker]()). * Explicit Duration: Wait duration in hours, minutes, and seconds. * Relative Duration: Wait duration in hours, minutes, and seconds before or after a specific time. Select Relative Duration to specify a wait duration from a specific date. Note: Past dates don't affect the wait duration. {#start-with-delay-properties__ul_mg2_ykw_fhc}You can enter a wait value of up to 999 hours. Note: The actual wait duration can vary due to the instance processing time. The playbook always waits for the time that you specify for this field, but other work in the queue may add to the wait time. |
| Wait for Percentage | Integer | Percentage of time to wait from a specified end date before running an activity or stage. You can manually enter an end date or select a date/time data pill from the data pill picker (![Data pill picker]()). If you select an end date in the past, the wait duration is set to 0. This field is only available when you set the Duration Type to Percentage Duration. |
| During the following schedule | Reference.Schedule \[cmn_schedule\] | Schedule used to calculate an end date that occurs during your hours of operation. For example, the calculated end date for a 10-hour duration that occurs during a 8-5 weekdays schedule will always be one or more business days in the future. If you leave this field blank, the calculated end date does not follow a schedule. For information on creating schedules, see [Define a schedule](https://www.servicenow.com/docs/access?context=t_DefineASchedule&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US). |
[ ]

{#start-with-delay-properties__table_ajt_sr3_plb}
**Related concepts**   

* [Activity definitions](https://servicenow-prod.fluidtopics.net/r014Lhz_11xoMRZZRHOzcA "Activity definitions describe how the activities in your playbook get the data that they need when your playbook runs.")
* [Automation Assets](https://servicenow-prod.fluidtopics.net/mU389THCpCX6TcjWJLTNJg "Include all automation assets in the activity picker to add a subflow, flow, or action directly to your playbook without having to create an activity definition.")
* [Optional activities](https://servicenow-prod.fluidtopics.net/pJEY3EDh5wh5XlpPOIG19Q#optional-activities "Enable your agents and fulfillers to add additional activities as they go through a playbook.")
* [Playbook activity state mapping](https://servicenow-prod.fluidtopics.net/fmXbaKoPUaBr1Y8dpLJFYA "Use playbook activity state mapping to override the status of a playbook card.")  
**Related tasks**   

* [Add and configure a stage in a playbook](https://servicenow-prod.fluidtopics.net/Vk3iDYyg_Df62zD4oj~nDQ "Add and configure a stage in your playbook.")
* [Add and configure an activity in a playbook](https://servicenow-prod.fluidtopics.net/eH66_4Re8HXK8adZ1kzWiw "Add and configure an activity in your playbook.")
* [Decision activities](https://servicenow-prod.fluidtopics.net/4rX5cqI_FXRlYNq~tfDHiQ "Create and define branches with different conditions for different paths that an agent can follow in playbook.")
* [Parallel branches](https://servicenow-prod.fluidtopics.net/PNev5QskKuGUAmoIHUw0fQ "Add branches for activities and stages that run in parallel to another branch of activities and stages.")
* [Add dynamic inputs to an activity](https://servicenow-prod.fluidtopics.net/8XnLc2y4MM0hKIntwpZR5A "Configure your activity to show a certain set of fields based on the value of another input, such as a selected catalog item, selected decision table, or even a REST API response.")  
**Related reference**   

* [Questionnaire activity](https://servicenow-prod.fluidtopics.net/0Zhk1Qtvq62no8BNvPsGbQ "Collects inputs from a user during a playbook run to use later in the playbook.")

