friends, forget about this. the problem is that large timeout numbers make setTimeout imediatly execute without any error or warning. so our user test tokens (which have many decades of expiration) trigger this odd behavior. tks.