There are a few possible blockers to your local Cycle client being able to connect to the license server and check out your license. Things to check include:
If your network requires a proxy connection, your Cycle administrator should provide you with the connection information.
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.
No. Closing Cycle will relinquish your license automatically.
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.
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.
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.
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.
A status code 590 occurs when Cycle is unable to communicate with the Cycle License server. This communication uses port 443 via TLS. This issue is most often caused by either local or network security settings. More information