Known issues

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

Known issues in DevOps Loop 2025.12 (2.0.0)

The known issues are as follows:

ID Description
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.
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.
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.
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.

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
NEXUS00003212

After a Build server or an agent pod restarts, the previously configured agents are no longer available in Build.

To work around this problem, you must reconfigure the agents manually from the Build UI after restarting any pod. For more information, refer to Configuring agents.

 1.0.3 1.0.3
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
NEXUS00003375

When you upgrade DevOps Loop from version 1.0.2 to version 1.0.3, teamspace creation might fail at the Build step if the teamspace contains existing build resources with naming conventions that conflict with the resources created during the upgrade.

To work around this problem, rename the conflicting resources in Build and then click the Retry option.

1.0.3 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
NEXUS00002053 When you navigate to Settings > User Administration > Users, and if you try to filter the user list by using the drop-down lists available on the page, the result might not display correctly. 1.0.2 1.0.3
NEXUS00002082 When you perform the following steps in DevOps Loop, you might see the error page instead of the DevOps Measure home page:
  1. Create a teamspace.
  2. Create a loop.
  3. Navigate to Measure.

    An error page is displayed.

To work around this problem, you must perform the following tasks:
  1. Configure nginx to increase its buffer size with the following values:

    proxy_buffer_size 32k;
    proxy_buffers  8 16k;

    Note: You can run the following commands to do the configuration:
    kubectl get pods | grep velocity-router
kubectl edit cm nginx-conf
kubectl delete pod <velocity-router-id>
  2. Verify whether the issue is resolved. If not, go to step 3.
  3. Resync the user's access by performing the following steps:
    1. Log in to DevOps Measure and delete the user from the team that is created through teamspace or loop by navigating to Settings > Users.

      The user can log in to Measure but loses access to teams and resources associated with the teamspace or loop in DevOps Measure.

    2. In DevOps Loop, add the user again through the teamspace and loop creation process.
 1.0.2 1.0.3
NEXUS00002086 When a teamspace owner invites an admin user through the invite process as part of the teamspace creation, and when the invited user logs in to DevOps Loop and navigates to DevOps Measure through the switcher, the login page displays instead of the home page of DevOps Measure.
To work around this problem, you must perform one of the following tasks:
  • Click Login with OIDC.
  • Clear your cache, cookies, and local browser data.
If the issue is still not resolved, resync the user's access by performing the following steps:
  1. Log in to DevOps Measure and delete the user from the team that is created through teamspace or loop by navigating to Settings > Users.

    The user can to log in to DevOps Measure but loses access to teams and resources associated with the teamspace or loop in DevOps Measure.

  2. In DevOps Loop, add the user again through the teamspace and loop creation process.
 1.0.2 1.0.3