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 |
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 ( Image omitted: data_pill_picker.png - 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. Data pill picker). For example, use a Look Up Record action to select an SLA Definition record and return the value of the <strong>Duration</strong> field.- <strong>Explicit Duration</strong>: Wait duration in hours, minutes, and seconds. 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 the Duration Type list. |
| 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 |
|---|---|
| Duration | Total time that the flow ran in milliseconds. You can drag this data pill into the duration fields. |
| Date/time | Date/time that the flow completed. You can drag this data pill into the date/time fields. |
Close an incident if it has been in the resolved state for 10 days
In this example, a flow starts when the incident state changes to Resolved.
Flow trigger.
Wait 10 days after the last update to a record
In this example, the flows waits for 10 days after the incident record has been resolved.
Wait for Duration flow logic.
Update a record after 10 days
In this example, the flows closes the incident record 10 days after it was resolved.
Action used to close the incident.
Wait for a duration of 50% of the time between the start of the flow logic and the due 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 and time, the schedule, and finally, the duration. Schedules, dates, and times set in the past don't 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
Example execution details for a wait for a duration flow.
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 it takes to execute the flow logic and doesn't 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.
Parent Topic:Workflow Studio flow logic
Related topics
Append to Flow Variables flow logic
Assign subflow outputs flow logic
Do the following until flow logic