Wait for a duration flow logic
-
- UpdatedJan 30, 2025
- 5 minutes to read
- Yokohama
- Create Workflows
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 |
|
| Wait for | Set this value manually or select a Duration data pill from the data pill picker
( ). For example, use a Look Up Record action to select an SLA Definition record and
return the value of the Duration field.
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. |
Example: 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.
Example: 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.
Example: Update a record after 10 days
In this example, the flows closes the incident record 10 days after it was resolved.
Example: 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.
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.
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 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.
On this page
- 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 the due
date
- Relative Duration type
- Execution details
Related Content
- Assign subflow outputs flow logic
Specify the data the subflow returns when it completes running. Use subflow output as data for a parent flow or as input for another process.
- Call a workflow flow logic
Run a published and active workflow from your flow. You can use the flow data as a workflow input. For example, you can specify the current record as a workflow input.
- Do the following until flow logic
Apply one or more actions repeatedly until an end condition is met. You can use the flow data to specify the end conditions.
- Do the following in parallel flow logic
Run actions and subflows in separate paths within an isolated flow logic block.
- Dynamic flows flow logic
Identify and run a flow or subflow dynamically by using runtime data. Build templates to provide expected inputs for dynamically called flows or subflows.
- End Flow flow logic
Stop running the current flow. Use End Flow within a branch of the flow to specify an exit condition. For example, end the flow when it reaches a specific If flow logic block.
- Exit Loop flow logic
Exit from a flow logic loop when the conditions of an If flow logic are met. Continue running the flow from the next step after the flow logic loop. This flow logic is also known as break.
- For Each flow logic
Apply one or more actions to each record in a list of records.
- Go back to flow logic
Return to a prior step in the flow to repeat a sequence of actions.
- If flow logic
Selectively apply one or more actions only when a list of conditions is met.
- Make a decision flow logic
You can use the decision table branching logic in situations where multiple conditional paths are required, as an alternative to nested If, Else If, or Else flow logic. For example, if you want to determine what kind of car insurance you need, you can add inputs such as your age, accident history, and car model to the decision table to determine a level of insurance coverage. This logic can save you time and present a more readable format than nested if conditions or switch case statements.
- Set Flow Variables flow logic
Assign a value to one or more flow variables, which store flow data as data pills. Access flow variable values by referring to their data pill.
- Skip Iteration flow logic
Skip the current iteration of a flow logic loop when the conditions of an If flow logic are met. Continue running the flow logic loop with the next item in the list. This flow logic is also known as continue.
- Try flow logic
Allow a flow to continue running when an error occurs within a flow logic block. Run a sequence of actions in response to errors within the flow logic block.