Troubleshoot the Argo CD Integration

Use this guide when Argo CD cannot connect or applications are not visible.

Argo CD shows as not connected

argocd_connection_health reports unhealthy or the application shows a failed connection. Possible causes:

• the integration was never connected;
• the API token was revoked or expired;
• the server URL is incorrect or unreachable from platform-api;
• TLS verification failed for the Argo CD certificate.

Re-enter the server URL and a valid read-only API token in IncidentFlow → Integrations → Argo CD.

Permission denied

Argo CD returns a permission error. Confirm the account's RBAC policy grants read (get/list) access to applications, resources, and history. Do not grant sync or admin permissions to resolve this.

Applications are not visible

Verify:

• the applications belong to a project in the configured scope;
• the read-only account can list the applications in Argo CD;
• the request resolves to the correct workspace and integration.

Collect diagnostic information

When contacting support, include the Argo CD server host, the affected application name, the approximate time, and the MCP request_id. Never include the API token or raw credentials.