We are an AWS solution provider, and our customer is using QuickSight.
The customer has its own customers, and end users report the same error several times. These layers exacerbate the debugging problem.
When they accept an invite, they receive an error that says “It’s not you, it’s us”.
Although this is cute, it provides no visibility into what went wrong. As end users are non-technical, they cannot also debug their own problems, and we, as the solution provider, get no visibility as to what went wrong and are completely powerless to provide any assistance.
As the result, the client is disliking QuickSight as it’s “too buggy”.
We’ve tried to eliminate any known issues, like expired invites (not the case), or browser settings (tried in Incognito mode), and the errors persist.
Any clues as to what this may be caused by? I’ve never seen this error before and especially not so many times.
IMO, the ideal solution would provide some unique ID (e.g. UUID) on the error screen, that the end users could share with us, and then we could, perhaps, have a CloudWatch log with all of the error details.
@m0ltar I spoke to the PM team. They recommend filing a case with AWS Support to look into this kind of issue – so that Customer Support can look at the logs. Here are the steps to open a support case. Note: If your company/customer’s company has someone who manages the AWS account, you/they might not have direct access to AWS Support and will need to raise an internal ticket to the IT team or whomever manages your AWS account.
I have some hints on what might be causing this issue; I just saw someone screen-share it. I think the users are also using AWS SSO, and when they get presented with the QS screen, it maybe somehow gets sessions mixed up. Not really sure, but just a small observation.
