Studio Desktop cannot load Integration Service connectors and activities

Workaround for Studio Desktop failing to display Integration Service connectors and activities due to a typecache routing issue in Automation Suite 2025.10.0–2025.10.2.

Note:

This issue affects Automation Suite 2025.10.0–2025.10.2. It is resolved in 2025.10.3.

Description

In Studio Desktop, the Activities panel does not list Integration Service connectors and activities. The intsvcs-periodic service logs contain the following error:

org.springframework.web.servlet.NoHandlerFoundException:
No endpoint GET /v3/element/typecache/api/Studio/Packages

This is caused by a routing misconfiguration: Studio Desktop requests connector information at the path /v3/element/typecache/..., but in-cluster routing forwards this request to the intsvcs-periodic service without removing the /v3/element prefix. The service has no handler registered for the prefixed path and returns 404 Not Found.

Note:

Studio Web is not affected by this issue.

Solution

Step 1 — Confirm you are affected

Run the following command to check the intsvcs-periodic logs for the 404 error:

kubectl -n uipath logs deploy/intsvcs-periodic -c periodic --since=1h \
  | grep "No endpoint GET /v3/element/typecache"

If the command returns output, you are hitting this issue.

Step 2 — Apply the VirtualService rewrite

1. Open the VirtualService (abbreviated vs in kubectl) for editing:

   kubectl -n uipath edit vs intsvcs-periodic-vs
   

2. Locate the rule named standard-url-periodic-elementPath and add the following two lines directly above the route: key:

   rewrite:
     uri: /
   

   After the update, the rule should look like this:

   uri:
     prefix: /v3/element/
   name: standard-url-periodic-elementPath
   retries:
     attempts: 3
     perTryTimeout: 20s
     retryOn: connect-failure,refused-stream
   rewrite:
     uri: /
   route:
     - destination:
         host: intsvcs-periodic.uipath.svc.cluster.local
         port:
           number: 80
   timeout: 60s
   

3. Save and close the editor. Kubernetes applies the change immediately.

Step 3 — Verify the rewrite

Run the following command to read the saved VirtualService definition and confirm the rewrite rule was applied. The command uses jq to extract only the rewrite field from the JSON output:

kubectl -n uipath get vs intsvcs-periodic-vs -o json \
  | jq '.spec.http[] | select(.name=="standard-url-periodic-elementPath").rewrite'

Expected output:

{
  "uri": "/"
}

Step 4 — Validate in Studio Desktop

Reopen the Activities panel in Studio Desktop and confirm that Integration Service connectors and activities now appear.