If I operate with a floating strict (team) license, do I have to request a license at the beginning of every work day?
No. Cycle will automatically request a license upon launching the application and authenticating a user. In addition, Cycle will request a license before executing a Feature File. Therefore, if you leave Cycle open over an extended period of time during which your license expires, you should not have to close Cycle to gain a new license.
If I operate with a floating strict (team) license, do I have to relinquish my license at the end of every work day?
No. Closing Cycle will relinquish your license automatically.
I'm able to log into my Cycle client but can't check out a license.
Being able to log into the Cycle client isn't the same as having a license. Licenses are assigned to users. You are able to log into the client because you have a valid user account, however could run into errors regarding checking out a license for a variety of reasons. Visit Error Messages for more detail.
Cycle is automatically signing into a previous account.
After signing in successfully to Cycle, the client will store an API key to bypass the login on future launches. If someone else logged into the same Windows user and still has a valid account, the API key associated with that device will still be valid. This will bypass the sign in process. To fix this, logout by going to Help > Logout in the top menu.
Can I use a node-locked license across PC user accounts on the same machine?
Cycle licenses are stored on a per PC user basis. Two different user accounts on the same machine would each need their own Cycle license.
Can I transfer my Cycle license between machines or copy an instance of my Virtual Machine with a Cycle license on it?
The API key that is generated for the respective Cycle license uses a unique hardware ID. Changing machines or running a copy of a VM will result in a new hardware ID and require a new API key.