Timer can behave differently depending on the scenario at with they are started. Some of the scenarios and Timer behavior is as described below.
For example:
A timer is configured to tick every 20 seconds. So this means that the timer will normally tick at the following times:
20, 40, 60, 80, 100, etc
Now let's say that on the second tick, the timed transaction took 25 seconds to complete. This means that the transaction which started at the 40 second mark completed at the 65 second mark, and is therefore deemed to have 'missed' the 60 second mark. So the next time the timer will tick will be at the 80 second mark. So the actual times the timer will have ticked are:
20, 40, 80, 100
For example, the user invokes a rather long online transaction which does the following:
Next the following will happen:
i.e. even though these timers were committed at the same time, each retains its own individual start time.