WebSocket connection failure when there are more than one embeddings

We are embedding 4 dahsboards in one page.
Loading them intermittently gives websocket connection error. But the message is coming from SDK.

I wonder if Quick Sight has a limitation that only allows 2 max embedding? I don’t think so but that’s what I see.

Sometimes all 4 dashboards show up but other times 2 of them are failing.
when it fails, it shows infinite loading icon with the above websocket error in the console.

So this works sometimes but not others?

I would suggest opening up a support case to AWS.

Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!

1 Like

@tbdori I faced with same issue. Did you found a solution?

Not really. I opened a support case with AWS. waiting for response
In the meantime we got it working by reducing 4 calls to 2 calls at the moment. Although we know this is not scalable as we will end up having many embedded visuals within one page pretty soon.

hi JC

Are these calls to the same dashboard or different dashboards?

It’s possible that there is throttling happening, which prevents more than 2 calls dashboard requests occurring at the same time.

thanks!

2 Likes

We had one visual per dashboard. So, they are all different dashboards.

But, still, this is good to know. Can you provide any reference link on the threshold?

We’re planning to create 5-10 visuals on one dashboard, then just embed visuals individually in the client side. FE will call with dashboardId and visualId .

Is this not going to work based on the throttling? Or, is it ok as long as we embed with visualId ?

Based on that - one thing to try is to add all visuals to one dashboard - and see if it provides any benefit when loading.

Ultimately if using visual embedding - experience should be better, specially when embedding/loading multiple assets in one page. Although there is a limit as long as it was queued (in calling app) to keep the parallel loads under threshold. Re threshold documentation currently there is no public information. For more details and if you need to request an increase please reach out to support and our engineers can worm with you to understand and support.

thanks!

1 Like