@v-siky-msft
Ah, thank you for clarifying.
So actually the trick is, the Timer is retrieving value of time passed, now it makes sense.
In your GIF now we understood why the old amount of time still showed for split second.
Because it was not a workaround to dormancy, it was a workaround to still keep track of amount of time being passed even after it was made dormant, and to update right away when made awake again.
So if suppose something had to actually happen when countdown ended exactly and while still dormant, this would not work.
However, it could still work, if it was OK for the countdown action to be performed immediately when the app is made awake again, even if it means it could be later than the literal countdown time (i.e. not until app was made awake again at the minimum).
This is great alternative solution @v-siky-msft considering the limitation.
This would be similar to something we might do under these conditions
Aside from your idea, we would be unsure how to do it while the app was dormant and countdown timer literally enforced even if it was dormant. Your alternative is very great though considering the limits.