When does the 'Timer Event' Skip an Input Task node? If I set

The timer is activated as soon as the process reaches the user input task node, even if no user has accepted the task yet. Thus, if it takes the user 40 minutes to complete a form that has a 30 minute exception timer, when submitting the form, the user will get a message indicating that the task has already been completed. Any work that they have done on the form will not be saved, as the process has already moved on.

The timer should be activated as soon as the process reaches that node (i.e. when the task is assigned, not accepted). When activity chained this is also the case. It will skip 30 minutes after being pushed to that node unless it is already submitted.

If the user took 40 minutes then the user would see the red warning box ("this task has already been submitted").

The timer event in User input task is activated as soon as task is active which can be either in Assigned or accepted state.

The timer event is activated as soon as the process reached the node even if it's activity chained.for you question the end user will receive the message "The task could not be submitted.Task has already been submitted." loosing all the data on the form.

Hi nickh647,

If your question is about scheduling Timer Event --

The User Input task node will get activated once the process flow reaches to it and waits for the given period of time.

Untill the given time is over, user cannot access that node. Once the timer gets completed, after that a user will be able to access the node.If a user tries to access before the completion of timer, throws error saying --- "The task status null is invalid".

Else,if it is about Escalations Timer Event --

Here we need to configure things like-- Reassigning the Task, Priority Of Task.

If the user has not submitted the user input task with in the escalation time, then the above configured things will happen.

As others have said, the user will not be able to submit the task because the flow has already expired.

If you want the user to still be able to submit the task, an alternative design should be used. For example, you could have your workflow go down two different paths before it reaches the form. One path could go to a timer, and the other to the user task. Both the timer and the task can then go to a complex gateway which will only continue the first time it is hit. This will allow the process to continue due to a form being submitted, but also allow the process to continue without the form being submitted while still saving the output of the form if it is eventually submitted.

The node gets skipped after the process reaches that node irrelevant of whether the user accepted or did not accept the task