Why Some Parts of the Cloudsoc/CASB Console App Might Not Load ?

Products

• CASB Gateway Advanced
• CASB Advanced Threat Protection
• CASB Audit
• CASB Gateway
• CASB Security Advanced
• CASB Security Advanced IAAS
• CASB Security Premium
• CASB Security Premium IAAS
• CASB Security Standard
• CASB Securlet IAAS
• CASB Securlet SAAS
• CASB Securlet SAAS With DLP-CDS

Issue/Introduction

You might have noticed that sometimes parts of the Cloudsoc console don’t load properly - like data not showing up, buttons not responding, or things just feeling stuck. The rest of the console might still look fine, but something clearly isn’t working right.

This isn’t a bug in the console UI/app itself, but rather a protection feature built into the browser (like Chrome or Edge) that’s trying to prevent too many things from happening at once.

Environment

Browsers affected: Google Chrome, Microsoft Edge (and other Chromium-based browsers)
When it happens: Usually when the app tries to load a lot of data very quickly
What you’ll see: Some parts of the app don’t load or update, even though the rest of the page looks normal

Cause

Chromium includes a request throttling mechanism designed to protect against "request storms." When a large number of requests are initiated in a very short time frame, the browser may halt further requests to maintain stability.

In observed cases, the browser throttled requests after detecting high number of requests within a window of few milliseconds. This threshold triggers an internal backoff mechanism, preventing additional requests from being sent temporarily. The UI continues to operate, but data fetching or background operations may silently fail.

Resolution

This is a known issue, and the application team is working on improving it so that the console does not hit the browser threshold, and it will be addressed in the next releases of Cloudsoc / CASB.

In the meantime, the workaround is to disable this feature at the browser level, by using the "--disable-extensions-http-throttling" switch.

Google Chrome:

chrome.exe --disable-extensions-http-throttling

 

Microsoft Edge:

msedge.exe --disable-extensions-http-throttling

 

make sure to close all the browser instances and then start it up with the above switch.

Additional Information

This throttling behavior is not configurable via browser UI.
It applies primarily to extensions and background scripts but can affect web apps with aggressive request patterns.
You can inspect throttled requests using chrome://net-internals or browser DevTools.
For production environments, always favor architectural changes over disabling browser protections.