This article is also available in:
Non-interruptive timers can only be associated to User Tasks and must be defined in the process workflow. To use non-interruptive timers, set a due date to establish when a task should be completed as well as a parallel path in the flow.

If the due date is reached and the task was not completed, the task will not be cancelled; rather, the flow will run in parallel by the path indicated through the timer and by the task the timer is associated to, which will remain active.

The following gif image will show you how to set up non-interruptive timers in a fast and simple way:

To use non-interruptive timers, set up parallel paths in your workflow (one or several), depending on the use you want to give them within your process. If you wish to know what are non-interruptive timers used for, visit the following post.

Warning: You may associate up to 5 timers per task.

To set up the due date of a non-interruptive timer, just double click on it. You can choose how many years, months, days, business days, hours, minutes or seconds you want to establish as due date before the timer is activated. You can also set up a timer according to an absolute date that will be taken dynamically from a Date type field.

When the timer is defined by business days, the Holidays and workdays settings will be considered

Possible issues

When you set up non-interruptive timers only to send a reminder, you should be really careful not to create a loop that generates a copy of the same process instance each time the timer is executed. If you model the following flow:

What will happen is that the system will create as many instances as times the non-interruptive timer has been executed. For this reason, if what you want is to send reminders indefinitely until the user completes a task, we advise you to click on the checkbox that executes the reminder indefinitely and to refrain from connecting the reminder to the task that needs to be completed.
Was this article helpful?
Thank you!