I agree the behavior seems to be somewhat random, and more often than every 30 days on some machines. The 30 day number came from support and I have not yet tried to track if that is actually what I am seeing.
I had zoom meeting with support this week and they again confirmed the only way to run automated tests without being logged out was to use the access key method. So far, since implementing this I have not seen my tests fail for this reason. I do however still get asked to login when I try to manually launch TC or TE, which is less problematic but still annoying.
I've never had TestComplete/Execute opened for more than 2 days, so I've never come across this issue before.
I guess the 30 day token is meant to reduce how often you need to re-authenticate while still keeping things reasonably secure. It's security vs convenience trade-off!
This makes no sense.
