Home New York Now Platform Capabilities Now Platform capabilities Flow Designer Flows Flow logic Wait for a duration flow logic

Wait for a duration flow logic

Use this flow logic to give your users time to act during automated processes or to wait for a specific date and time to complete actions.

Inputs


Input	Description
Duration Type	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 flow start. Percentage Duration: Type to specify a certain percentage of time duration between the start of the flow logic and specified end time. Note: The percentage value must be from 0 through 100 only.
Wait for	Set this value manually or select a Duration data pill from the 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. 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 flow 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	Wait duration as a percentage of the time period between the start of flow logic and specified end time. If you select a past date for the end time, the wait duration is set to 0. This field appears when Percentage Duration is selected from Duration Type.
During the following schedule	Select the schedule used to calculate the Scheduled End date/time value from the selected wait duration. For example, waiting for a 10-hour duration as part of an 8-5 weekdays schedule causes the flow to wait for one or more business days. If you leave this field blank, the timer runs without a schedule. For information on creating schedules, see Define a schedule

Outputs


Output	Description
Total duration	Total time that the flow ran in milliseconds. You can drag this data pill into the duration fields.
End at time/date	Date/time that the flow completed. You can drag this data pill into the date/time fields.

Example: Close an incident if it has been in the resolved state for 10 days

In this example, a flow starts when an incident changes to resolved.

Example: Wait 10 days after the last update to a record

In this example, the flows waits for10-days after the incident record has been resolved.

Example: Update a record after 10 days

In this example, the flows closes the incident record10 days after it was resolved.

Example: Wait for a duration of 50% of the time between the start of the flow logic and end date

In this example, the flows send a notification email to the relevant manager when a critical problem is created and 50% of the time between the problem record creation and the problem due date has lapsed.

Wait for percentage time duration flow logic.

Relative Duration type

When the duration type is Relative Duration, the flow logic first evaluates the relative date/time, the schedule, and finally, the duration. Schedules and date/times set in the past do not affect the wait duration. This table provides examples of how the flow processes the wait duration in these scenarios.


Duration Setting	Relative Date/Time	Schedule	Effect
Set to 0.	None	None	Duration ends immediately.
Greater than 0.	Past date	None	Duration ends immediately.
Greater than 0.	Future date	None	Flow waits for the date/time, and then waits for the duration.
Greater than 0	Past date	Future date	Flow waits for schedule, and then waits for the duration.
Greater than 0.	Future date	Past date	Flow waits for the date/time, and then waits for the duration.
Greater than 0.	Future date	Future date	Flow waits for the future date, then for the schedule, and then for the duration.

The timer waits for the next instance of a selected schedule. For example, if you set a schedule for Monday through Friday from 8 a.m. to 5 p.m., and the timer is initiated on Saturday, the timer waits until Monday at 8 a.m. before starting.

Execution details

The header shows the state, start time, and runtime for the flow logic.
Note: The runtime value in the header only includes the time that is taken to execute the flow logic and does not include the wait duration that is specified in the flow.
The Configuration Details section shows details about the variables that are used by the flow, including the type, configuration, and runtime values for each variable.

Previous topic

Next topic

Send feedback

Release version

Wait for a duration flow logic

Use this flow logic to give your users time to act during automated processes or to wait for a specific date and time to complete actions.

Inputs


Input	Description
Duration Type	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 flow start. Percentage Duration: Type to specify a certain percentage of time duration between the start of the flow logic and specified end time. Note: The percentage value must be from 0 through 100 only.
Wait for	Set this value manually or select a Duration data pill from the 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. 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 flow 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	Wait duration as a percentage of the time period between the start of flow logic and specified end time. If you select a past date for the end time, the wait duration is set to 0. This field appears when Percentage Duration is selected from Duration Type.
During the following schedule	Select the schedule used to calculate the Scheduled End date/time value from the selected wait duration. For example, waiting for a 10-hour duration as part of an 8-5 weekdays schedule causes the flow to wait for one or more business days. If you leave this field blank, the timer runs without a schedule. For information on creating schedules, see Define a schedule

Outputs


Output	Description
Total duration	Total time that the flow ran in milliseconds. You can drag this data pill into the duration fields.
End at time/date	Date/time that the flow completed. You can drag this data pill into the date/time fields.

Example: Close an incident if it has been in the resolved state for 10 days

In this example, a flow starts when an incident changes to resolved.

Example: Wait 10 days after the last update to a record

In this example, the flows waits for10-days after the incident record has been resolved.

Example: Update a record after 10 days

In this example, the flows closes the incident record10 days after it was resolved.

Example: Wait for a duration of 50% of the time between the start of the flow logic and end date

Relative Duration type


Duration Setting	Relative Date/Time	Schedule	Effect
Set to 0.	None	None	Duration ends immediately.
Greater than 0.	Past date	None	Duration ends immediately.
Greater than 0.	Future date	None	Flow waits for the date/time, and then waits for the duration.
Greater than 0	Past date	Future date	Flow waits for schedule, and then waits for the duration.
Greater than 0.	Future date	Past date	Flow waits for the date/time, and then waits for the duration.
Greater than 0.	Future date	Future date	Flow waits for the future date, then for the schedule, and then for the duration.

Execution details

The header shows the state, start time, and runtime for the flow logic.
Note: The runtime value in the header only includes the time that is taken to execute the flow logic and does not include the wait duration that is specified in the flow.
The Configuration Details section shows details about the variables that are used by the flow, including the type, configuration, and runtime values for each variable.

How search works:

Topics are ranked in search results by how closely they match your search terms

Wait for a duration flow logic

Wait for a duration flow logic

Inputs

Outputs

Example: Close an incident if it has been in the resolved state for 10 days

Example: Wait 10 days after the last update to a record

Example: Update a record after 10 days

Example: Wait for a duration of 50% of the time between the start of the flow logic and end date

Relative Duration type

Execution details

On this page

Wait for a duration flow logic

Wait for a duration flow logic

Inputs

Outputs

Example: Close an incident if it has been in the resolved state for 10 days

Example: Wait 10 days after the last update to a record

Example: Update a record after 10 days

Example: Wait for a duration of 50% of the time between the start of the flow logic and end date

Relative Duration type

Execution details

Log in to personalize your search results and subscribe to topics