Known issues

You can find the known issues that are identified in this version of HCL DevOps Loop.

Known issues in DevOps Loop 2026.03 (2.0.1)

The known issues are as follows:

ID Description
NEXUS00004833 When you create a segment, and the Plan component fails, both Retry and Done options might appear enabled. When you click Retry, the segment is created successfully; however, when you click Done, the progress view closes while the segment continues to get created in the background.

To work around this problem, when you click Retry, you must wait for the retry process to complete. During this time, the Retry and Cancel buttons are displayed.
NEXUS00005067 When you run the list test command, the response returns only the count of projects instead of detailed test information such as test names, IDs, or metadata. In some cases, the returned data might also be inaccurate.

Also, when you run a test prompt, the system might return a test asset file not found error even when the correct project ID and test name are provided, indicating an issue in locating or mapping the specified test file.

Currently, there is no work around to this problem.

Known issues from earlier versions

The known issues identified in the earlier versions of DevOps Loop that are still applicable are as follows:

ID Description Indetified in version Applicable in and until version
NEXUS00004152 When you receive a clarification question from Loop Genie, the test box might not get enabled, preventing you from entering a response.

To work around this problem, you must close and restart Loop Genie.

 2.0.0 2.0.1
NEXUS00004133 When you use IBM watsonX, it might not provide proper responses for multistep workflows. The issue is currently observed only with workflows involving multiple steps. Single-step workflows work as expected.

To work around this problem, you must use IBM watsonX only for single-step workflows until the issue is resolved.

 2.0.0
NEXUS00004078 When loop creation fails, and the API returns a message indicating multiple workflows with the same name (for example, "Multiple workflows found with the same name: Space1~LoopM"), two or more VSMs might get created with the same name. A duplicate VSM can cause failures in subsequent loop creation attempts.
To work around this problem, you must perform the following steps:
  1. Go to the Measure page and identify the duplicated VSM.
  2. Delete one of the duplicates, ensuring that only one VSM with that name remains.
  3. Return to the Loop home page and click the Retry button to create the loop again.
 2.0.0 2.0.1
NEXUS00003988 When you use Claude Desktop, the application might occasionally encounter connection issues due to a session timeout. Claude Desktop does not currently prompt the user to re-authenticate or refresh the session automatically.

To work around this problem, you must reconnect the connector to restore the connection. If reconnecting fails, you must delete the existing connector and create a new one, and then restore the connection.

 2.0.0 2.0.1
NEXUS00003275 When an administrator is added to a loop by another administrator before logging into Measure for the first time or before creating their own Loop, the administrator cannot log in to Measure.

To work around this problem, you must log in to Measure as another administrator (for example, the one who created the loop) and assign the global Product Administrator role to the administrator who cannot log in.

 1.0.3
NEXUS00001925 When a user is invited through the add user process as part of teamspace management, and then the user completes the sign-up process after clicking the invite link received over email, DevOps Loop displays just the confirmation message instead of displaying the login link.

To work around this problem, the user must manually enter the URL to log in to the platform.

 1.0.2