I’ve noticed that it doesn’t matter whether I create the action using QS authoring or whether I create the action on the fly using the SDK. I’ve also noticed that the error doesn’t have any impact on dashboard performance at all - my actions all still work.
That being said, I’d like to trace the source of the problem and resolve it, if possible. Has anyone else had this error come up, and have they been able to resolve it? Thank you!!
Hello @ltaylor, I am curious, does the action seem to be working as expected in the embedded dashboard or does it stop working once you embed it? If it isn’t causing any issues from the reader’s perspective, it is likely some not an issue.
I would honestly recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the [steps to open a support case](https://filing a case with AWS Support where we can dive into the details so that we can help you further. 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!). 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.
Since this may be a bug with actions, I think it would be good to submit the support case just in case. I hope this helps!
That’s just the thing: everything (as far as I can tell) is still working, so this error doesn’t really indicate a “problem” (at least, not to me) - it just seems to be there.
I have opened a support case as well but I haven’t heard back from them yet (the case is still unassigned, and it’s been a few days), so I’m just covering all of my bases to check everywhere I can with the question.
If possible can this be left open for a few more days to see if anyone else has encountered this issue in their embedded dashboards and, if so:
was there something you were able to do to resolve it (suppress or stop the error from occuring), or
do you have any more information about why it is happening in the first place?
From AWS Support. According to the “internal team”:
"There is a check on getStorage method which will return false if it an embedding page, so the error is bound to happen and there is currently no plan to fix this console error. "
Hello @ltaylor, thank you for taking the time to follow-up on this issue! While that is an unfortunate response, at least you were able to find some information on the problem.
