Hi All,
Here I would cover a very good example of how we can use the duration types in Flow Designer with a live examples as well.
Example: Wait for a duration of 50% of the time between the start of the flow logic and the due date
In this example we will see, the flows send a notification email to the relevant manager when a critical priority 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.
| 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
Execution details for Wait for a duration 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.
Hope it helps you.
I hope this article helpful. Please mark it as helpful and bookmark if you like it.
Regards,
Shamma
