On Automation Suite deployed on EKS, the Integration Services connector catalog is empty for all users including Organization Admins. All requests to the connector catalog and Automation Ops policy endpoints fail with HTTP 400 errors.
Issue Description
On Automation Suite deployments on EKS, the Integration Services connector catalog is empty for all users including Organization Admins. All connector catalog and Automation Ops policy requests fail with HTTP 400 errors. The following endpoints fail between the intsvcs-periodic and intsvcs-connectors-cluster-storage services, despite connector content being present in the cluster-storage pod:
GET /elements_/v3/element/elements/available-connectors-from-cluster-storageGET /elements_/v3/element/publish/active/publish-jobs
Symptoms
- The connector catalog in 'Integration Services' is empty for all users, including Organization Admins.
- All requests to the connector catalog return HTTP 400 errors.
- Automation Ops policy requests fail with HTTP 400 errors.
Resolution
Important: These steps require kubectl access to the Automation Suite cluster. Perform on EKS — the namespace may differ from standard Automation Suite deployments.
Step 1 — Pause ArgoCD auto-sync for Integration Services
Prevents ArgoCD from reverting the fix automatically.
kubectl -n argocd patch applications.argoproj.io integrationservices \
--type merge \
-p '{"spec":{"syncPolicy":{"automated":null}}}'
Step 2 — Back up the current configuration
Always take a backup before making changes.
kubectl -n uipath get cm intsvcs-periodic-application-properties \
-o yaml > /tmp/periodic-cm.yaml
Step 3 — Apply the fix
Open the ConfigMap for editing:
kubectl -n uipath edit cm intsvcs-periodic-application-properties
Locate and replace the property as shown below:
Remove this line | Replace with these two lines |
server.max-http-header-size: 32KB | server.max-http-request-header-size: 32KB server.tomcat.max-http-response-header-size: 32KB |
Step 4 — Restart the periodic deployment
kubectl -n uipath rollout restart deploy intsvcs-periodic
Wait for rollout to complete (~1–2 minutes):
kubectl -n uipath rollout status deploy intsvcs-periodic
Step 5 — Validate the fix
Confirm the 32 KB limit is now active:
POD=$(kubectl -n uipath get pods --no-headers | \
awk '/^intsvcs-periodic-[0-9a-f]/ && /2\/2/ && /Running/{print $1;exit}')
for sz in 9000 20000 31000; do
kubectl -n uipath exec $POD -c periodic -- sh -c \
"B=\$(head -c $sz /dev/zero|tr '\0' A); curl -s -o /dev/null \
-w '${sz}B=%{http_code}\n' -H \"X-Big: \$B\" \
http://localhost:8086/v3/element/elements"
done
Expected output — all three must return 200: 9000B=200 20000B=200 31000B=200 |
Step 6 — Verify in the UI
- Navigate to 'Integration Services' — the connector catalog should now populate.
- Navigate to 'Automation Ops' > 'Integration Services' policy — the HTTP 400 error should be resolved and policies should save successfully.
Note: ArgoCD auto-sync has been paused as part of Step 1. Do not re-enable it until a permanent fix is available in a future Automation Suite release — re-enabling will revert this workaround.