The CSPGatewayLatency alert indicates that the latency experienced in the CSP gateway exceeded the predefined maximum value. Here are the details:

1. Understanding CSPGatewayLatency Alert: CSPGatewayLatency measures the delay involved in processing requests between the CSP gateway and your web server. The alert you received indicates that the latency has far surpassed the maximum allowable value (2000 ms), reaching values exceeding 5000 ms. This suggests a significant performance issue potentially caused by a delay in processing requests made to the web server or server-side resources [1][2].
2. Relation to Server Response Timeout: While your suspicion linking CSPGatewayLatency to server response timeout is reasonable, these are distinct metrics. The Server Response Timeout is explicitly the maximum allowed time for the target InterSystems IRIS or Caché server to respond to incoming requests. On the other hand, CSPGatewayLatency is broader, detecting higher geometry dash game latency in communication specifically at the gateway level, which could result from multiple latency factors, not just server response time exceeding its timeout [1].
3. Investigating and Managing This Alert: a. Check logs (e.g., WebGateway Event Log) for more in-depth details about what requests might be causing increased latency [3]. b. Examine server-side performance metrics to identify potential bottlenecks—this could involve queries or processes that exceeded the Server Response Timeout set in your configurations [1][2]. c. Assess current CSP Gateway configuration, such as limits on server connections (max connections restrictions) and adjust as needed [2].

Upon troubleshooting, you may identify that specific CSP requests or load on your server resulted in slow response times. You can address server-side bottlenecks, optimize database queries or increase relevant timeout thresholds cautiously.
 

Sources:

1.Description of each timeout value that can be set in the default parameter of Web gateway/CSP gateway management

2.Settings in All Business Processes | Configuring Productions | InterSystems IRIS Data Platform 2025.2

3.CSPServer [css] Error setting up server

if your VS Code with the InterSystems Language Server isn’t fetching the namespace list, and you’ve confirmed the namespace exists and api/atelier is enabled, the next things to check are usually around connection config +network/auth:

make sure settings.json has the correct server, port, scheme (http vs https), and snowrider credentials. even small typos or wrong case in username/password can block fetching.

try using “Choose Server and Namespace” in ObjectScript Explorer — sometimes the cached connection info trips the extension up.

check for any firewall or proxy on Ubuntu ARM64 that could be blocking the VS Code extension from reaching the web app.

confirm the extension version (2.8.0) is fully compatible with IRIS 2024.3; occasionally newer IRIS builds need the latest language server release.

basically, the extension looks fine, so it’s almost always a config or network hiccup, not a namespace/server issue.

Good troubleshooting checklist. I’ve also seen cached workspace settings cause weird namespace issues, so recreating the connection profile sometimes fixes it immediately.

Hey Colin.

I had a few minutes before a meeting so wanted to try recreate on IRIS instead of Cache and happened to have not yet restarted VSCode so didn't have the new extension versions installed.

I was able to run the example you tried in the old extension versions and observed no errors moto x3m in the output for the language server, ran my updates, and then lost the ability to select the Language Server from the Output selection dropdown:

I would have liked to been able to completely recreate this in the new version, or at least give some indication of where the fault may be. But not being able to see the Output window for the language server like in your screenshot stops me in my tracks 😅

Hi Tim

Thanks, we don't currently use IPM.

So essentially if we want to use this we would need to change our current namespace setup and create a development namespace for each developer, plus one basketball stars for the master repository. Then for testing if we wanted multiple testers wanting to test multiple branches at the same time, presumably they'd also need a separate namespaces?

The settings I have in my outgoing namespace are:

and the settings I have in my incoming namespace (where I was trying to pull the project to) are:

I did originally have the settings for the receiving namespace very similar to the outgoing, but when I saw that the exported files had all been put underneath the csp directory I changed them to the above, but they still didn't import. 

The error I am getting is "Unable to import file *** as this is not a supported type"

thanks

From my experience, git-source-control works best with separate dev namespaces per developer. Shared namespaces cause conflicts. For static files (.js, .css, .png), import isn’t natively supported yet—you’ll need custom handling or a workaround script.