--- sourceDocument: Zurich Build workflows sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/build-workflows Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # Start with delay input properties # Start with delay input properties {#ariaid-title1} Release version: Zurich Updated July 31, 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 property in ServiceNow playbooks allows you to specify a waiting period before an activity or stage begins, even after its start conditions are met. This feature helps you give users time to act during automated playbooks or to wait until a specific date and time to complete actions. It is available for all stages and common activities except the Placeholder activity. Show full answer Show less ## Roles and availability Users with the roles **admin** , **playbook.admin** , **pdauthor** , or **pdcontentauthor** can configure the "Start with delay" input properties. ## Configuring input properties To enable and configure the delay, open an activity or stage's properties panel, access additional options, and enable the "Start with delay" setting. This reveals the following key configuration options: * **Duration Type** : Choose how to specify the delay duration: * **Explicit Duration**: Wait for a fixed time period (e.g., 5 minutes). * **Relative Duration**: Wait relative to a selected date/time or duration data pill (e.g., 5 minutes after the playbook starts). * **Percentage Duration**: Wait for a percentage (0-100%) of the time between the start of the activity or stage and a specified end time. * **Wait for Template Value**: Set the actual wait duration manually or select a duration data pill. For explicit and relative durations, specify hours, minutes, and seconds. Relative Duration allows waiting before or after a specific time. * **Wait for Percentage**: When using Percentage Duration, specify the percentage of time to wait and provide an end date or select a date/time data pill. If the end date is in the past, the wait duration defaults to zero. * **During the following schedule**: Optionally select a schedule (cmnschedule) to ensure the wait respects business hours, such as weekdays 8-5. If left blank, no schedule is applied to the delay calculation. ## Important notes * Maximum wait duration can be up to 999 hours. * Actual wait time may vary due to instance processing delays; however, the playbook waits for the specified duration. * Past dates used in relative or percentage durations do not extend the wait. ## Practical benefits for ServiceNow customers By leveraging the "Start with delay" input properties, customers can better control the timing of playbook activities and stages, accommodating user actions and business schedules. This flexibility enhances automation workflows by allowing precise timing controls aligned with operational needs and schedules. 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=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | [ ] {#start-with-delay-properties__table_ajt_sr3_plb} **Related concepts** * [Activity definitions](https://www.servicenow.com/docs/hC2JPXxYVpwMpyvSURl_5w "Activity definitions describe how the activities in your playbook get the data that they need when your playbook runs.") * [Automation Assets](https://www.servicenow.com/docs/L67AP3dqWmiE_EenylU4QQ "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://www.servicenow.com/docs/MoXZAJ9pnHGnDduCBfexng#optional-activities "Enable your agents and fulfillers to add additional activities as they go through a playbook.") * [Playbook activity state mapping](https://www.servicenow.com/docs/TxmkEZ31OOJd6i3fec3cRw "Use playbook activity state mapping to override the status of a playbook card.") **Related tasks** * [Add and configure a stage in a playbook](https://www.servicenow.com/docs/eGbgfOMGuzh4FN9SQEsjGA "Add and configure a stage in your playbook.") * [Add and configure an activity in a playbook](https://www.servicenow.com/docs/NbXwzuPJ~aGBcYZeOqq4Dw "Add and configure an activity in your playbook.") * [Use AI agent as an activity](https://www.servicenow.com/docs/ooMWuQV3n4XRlAE6~TT0AQ "Use an existing AI agent as an activity in your playbook to automate tasks. The AI agent gathers the required context, performs the work, and produces outputs that subsequent activities can consume.") * [Use an AI skill as an activity](https://www.servicenow.com/docs/VDJSJlQFDQCJVIC43XokNw "Use an existing AI skill as an activity in your playbook to perform lightweight, focused AI tasks. When the playbook reaches the activity, the skill runs, produces structured outputs, and passes those outputs to subsequent activities.") * [Decision activities](https://www.servicenow.com/docs/QyHxbYwM6qhzqDzb~Wc9KQ "Create and define branches with different conditions for different paths between activities.") * [Decision stages](https://www.servicenow.com/docs/S4pK7SF48XPb4Tso9rn_vQ "Create and define branches with different conditions for different paths between stages.") * [Parallel branches](https://www.servicenow.com/docs/xmTen~VpUFkYSmESNMMUjg "Add branches for activities and stages that run in parallel to another branch of activities and stages.") * [Add dynamic inputs to an activity](https://www.servicenow.com/docs/63bEPdFvWFmUcskvj3zH5w "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://www.servicenow.com/docs/Gm_0SxqbZGe5zYGiIJa0SQ "Collects inputs from a user during a playbook run to use later in the playbook.")