Cycle 2 Install FAQ

Cycle 2 Install FAQ

The Cycle install process and post-install authentication process has changed as of the release of Cycle 2.9.2. This process applies to Cycle 2.9.2 and all future versions of the Cycle 2 Application.

This article contains frequently asked questions about the updated installation process and issues that may arise during installation and authentication.

How often do I need to re-enter my Cycle Cloud credentials into Cycle and reauthenticate?

Once you are logged into Cycle 2.9.2+ using your Cycle Cloud credentials, the access token will be valid for 8 hours. 

If the machine Cycle 2.9.2+ is installed on has the ability to reach the Azure B2C authentication instance, a new access token will be silently acquired when the existing one expires. This new access token is acquired via a refresh token which is valid for 90 days. 

If the machine Cycle 2.9.2+ is installed on is behind a firewall or cannot reach the Azure B2C authentication instance for some other reason, the user will need to find an Internet connection that can reach Azure B2C and log in (to get a new access token). They will then be able to use Cycle for 8 hours on that machine without having to reach Azure B2C (i.e., behind the firewall).

Closing Cycle on a machine and reopening it will not require you to log in again if the access token is valid. 

What URLs do I need to whitelist to ensure Cycle 2.9.2+ can always reach the Azure B2C authentication instance?

Customers who want to whitelist our Azure B2C authentication instance should whitelist the following URLs:


Please refer to this article for a simple test you can run on your device to ensure network traffic to the Azure B2C URLs is not being blocked: Testing Cycle Authentication URLs

When I enter my Cycle Cloud credentials, close the browser, and return to Cycle, the authentication modal still shows a “spinning” icon, and I still cannot access Cycle. What should I do?

1. Verify that the machine Cycle is installed on is using an Internet connection that can reach Azure B2C and log in (to get a new access token). For more information, see “ How often do I need to re-enter my Cycle Cloud credentials into Cycle and reauthenticate? ”.

2. Verify that you have an active Cycle license by contacting Cycle Customer Care at  help@cyclelabs.io .

3. If Cycle is not able to authenticate with Cycle Cloud via the default web browser or Cycle is closed in the middle of the authentication process, then Cycle can become locked in a "waiting for authentication" state. 
When a user closes Cycle in the middle of authentication, the Cycle processes that were running do not stop. This means subsequent attempts to open Cycle fail to start a new instance, because the Cycle UI checks to be sure only one Cycle UI is running at a time.

This issue can be resolved by taking the following steps:
1. Manually close the cycle window.
2. Navigate to the Process tab in Windows Task Manager.
3. Find two services labeled "Connecting" and "cycle-client".
4. Right click and select "End Task" for the two processes.
5. You should now be able to open Cycle again and restart the Cycle Cloud login process.
6. If the browser window continues to be blocked from opening or the Cycle Cloud login page is not loading, please contact help@cyclelabs.io for assistance.
4. If for some reason that does not resolve the issue, or you have another issue, please contact your existing point of contact (if you have an active Cycle Labs project) or reach out to Cycle Customer Care at  help@cyclelabs.io .

When I open Cycle, it gets stuck on a modal that says "Loading Cycle resources...", and Cycle never opens. What should I do?

If a user does not uninstall previous versions of Cycle when upgrading to Cycle 2.9.2 or higher, desktop and Start menu shortcuts may point to an old version of Cycle that is now expired. 

Uninstalling previous versions of Cycle should solve this issue.

If the shortcut you click to open Cycle points to a path that includes “\Tryon Solutions\”, then that shortcut is definitely pointing to an old version of Cycle.

What if the Cycle login window doesn't open or is closed before I can login with my Cloud Credentials?

If Cycle is not able to authenticate with Cycle Cloud via the default web browser or Cycle is closed in the middle of the authentication process, then Cycle can become locked in a "waiting for authentication" state. 
When a user closes Cycle in the middle of authentication, the Cycle processes that were running do not stop. This means subsequent attempts to open Cycle fail to start a new instance, because the Cycle UI checks to be sure only one Cycle UI is running at a time.

This issue can be resolved by taking the following steps:
1. Manually close the cycle window.
2. Navigate to the Process tab in Windows Task Manager.
3. Find two services labeled "Connecting" and "cycle-client".
4. Right click and select "End Task" for the two processes.
5. You should now be able to open Cycle again and restart the Cycle Cloud login process.
6. If the browser window continues to be blocked from opening or the Cycle Cloud login page is not loading, please contact help@cyclelabs.io for assistance.

Who should I contact if I have questions about upgrading to Cycle 2.9.2?

If you are a customer with an active project with Cycle Labs, please work through existing points of contact at Cycle Labs to complete the migration.

If you are a Cycle Labs partner, please contact Jonathan Yiv at jonathan.yiv@cyclelabs.io to work through any questions that will enable you to support your customers with the migration to Cycle 2.9.2. 

If you do not have an active project with Cycle Labs, or if you do not know who to contact for assistance, please reach out to Cycle Customer Care at help@cyclelabs.io.

Who needs to upgrade to Cycle 2.9.2?

All Cycle users, including customers, partners, and Cycle Labs employees.

What benefit will customers receive from upgrading to Cycle 2.9.2 and creating a Cycle Cloud account?

Upgrading to Cycle 2.9.2 will enable you to continue using Cycle after March 1, 2022, since pre-2.9.2 versions of Cycle stopped working after that date.

The release of Cycle 2.9.2 also kicks off our incremental move toward the cloud, leveraging more modern architecture to improve scalability and performance, and enabling us to seamlessly release product improvements and updates on a more regular basis.

Cycle 2.9.2 also includes a bug fix, three new Steps, and updated Help Menu links. See the Release Notes for more details.

Where will I go to download Cycle 2.9.2, the Test Library, and the Cycle Appliance after the User Portal has been sunsetted?

Download Cycle 2.9.2 and access the Cycle Appliance by clicking the links below.


For the BY Test Library, please contact help@cyclelabs.io.

What changes are needed to make the Cycle Appliance work with Cycle 2.9.2?

The Cycle Labs custom image used to deploy test agents in Cycle Appliance pipelines will be updated with the Cycle 2.9.2 release. This image will include a full install of Cycle 2.9.2 as well as an updated PATH environment variable to reflect the new install location of Cycle 2.9.2. 

Any customers using the most recent version of the Cycle Appliance that takes advantage of our custom images should not be impacted by the change. Cycle-CLI does not require authentication to execute tests. This means a test agent can be provisioned using our custom image and Jenkins will be able to execute Cycle-CLI tests on that image without any sort of manual intervention. 

If you are specifying the full path to the Cycle-CLI.exe in their pipeline execution code, you will need to update that path to the new install directory. However, this shouldn’t be necessary if you have written their commands without specifying the path to Cycle and relying on the system PATH to include the Cycle install directory.

If you connect to a Cycle Appliance test agent desktop or deploy a Cycle custom image VM for the purpose of using the Cycle Client, you will be required to authenticate in order to use the Cycle 2.9.2 Client.

If you are not using the Cycle custom image to provision test agents, you will need to update your repositories with a Cycle-CLI.zip containing Cycle 2.9.2. This will replace your current Cycle version with the latest Cycle version.

What should I do if I get a Windows Defender Firewall message when installing Cycle 2.10 and newer versions?

Cycle version 2.10 is built using a newer version of Java and Cycle now distributes with OpenJDK included in the install package. You may get a message when first opening 2.10 after installation that indicates Windows Defender Firewall has blocked some features of this app. Click "Allow Access" to permit Cycle to use the java executable that is distributed with the Cycle application.



    • Related Articles

    • Cycle 2 Install Guide

      This article covers the process of installing the Cycle Client on your device and the steps required to authenticate using your Cycle Cloud credentials. The release of Cycle 2.9 kicked off our incremental move toward the cloud, leveraging more modern ...
    • Testing Cycle Access Token URLs

      Cycle requires an access token associated with a license in order to use the application.   It is necessary for the Cycle application to communicate with Azure B2C to secure this access token. Certain firewall or proxy configurations on your ...
    • How to resolve "Windows Protected Your PC" message when installing Cycle

      Occasionally, when first running the Cycle installer, the following error message may be encountered.     To resolve this issue, simply click on the "More info" link.  That will display more information about the app that is being prevented from ...