Unable to load this page: Please check your network connection or go back (embedding issue) -- BUG: relative date of "yesterday" while embedding

Question & Answer
, ,
1

Hello,

We have been using QuickSight for about 6 months now, and have been used the same Dashboard for months and suddenly started to get the above message when embedding. No reference to it online anywhere, anyone else running into this issue? I narrowed it down to Custom SQL (not related to the underlying DB, because 2 of our dashboards which uses Athena and RDS are both having the same issue, only when using parameterized Custom SQL). I tried the following without any luck:

  • Removed all visuals
  • Tried embedding directly in QuickSight (by using the Copy Link button), instead of using the API using get_embedded_url_for_registered_user
  • Published a new Dashboard from Analysis
  • Even re-created the same Analysis by copying each Data Source connection, copy the Analysis by using a template (using the API) and publishing a new Dashboard

qs-issue-2
qs-issue-21843Ă—828 11 KB

Again, dashboard works fine when I view it directly in QS, but embed fails. However, when I remove the DataSet that is using the Custom SQL it works.

Update 2

I narrowed it down to Parameters being added to Custom SQL. My results so far:

  • removed the Parameter reference in SQL (same issue)
  • removed parameters entirely from the Dataset, published a new Dashboard (ISSUE GONE)
  • added parameters with different names (ISSUE is BACK)

Update 3

The issue only seems to happen when I add AND map a date parameter. I tried mapping a string parameter and the issue is gone. I tried adding a date parameter and even tried mapping to a new date parameter and the issue is back.

Update 4

I further narrowed it down to Date parameter when the Default value is set to Relative Date

Update 5 - Bug Found

This is indeed a bug in QuickSight, in order to reproduce the issue, please follow the steps below (Update 6: You need to be in us-east-2):

  1. Create a new DataSource (I have tried, SQL, S3, and CSV) with Date Parameter. IMPORTANT to have a date parameter.
  2. Create a Visual with the DataSource and map to above created date parameter
  3. IMPORTANT: Set the Default date to Relative Date: Yesterday/Today
  4. Publish the Dashboard
  5. Share Dashboard
  6. Copy Link
  7. Open a new tab, paste the link, BOOM, bug

Update 6 - Bug Found (more info.)

I tried the same thing on a different region (other than us-east-2) and everything works fine. So it only seems to be happening in us-east-2. Tried two different accounts. us-east-1 works fine, us-east-2 fails.

Update 7 - Bug Found (more info.)

I contacted Amazon and they acknowledged it’s a misconfiguration on us-east-2 and escalating the issue. It is ONLY happening when you use “Yesterday” as relative date and while mapped to a DataSet parameter. Awaiting reply…

2

@ppuvan ,

thanks for the update. I understand you have a logged a ticket with support, please update this question once it’s resolved.

Kind regards,
Koushik

3

I’m in eu-west-1 and I’m having the exact same issue with embedded dashboards that use direct query as the query mode. All of our direct query dashboards need to use date parameters otherwise we will be pulling years worth of data that will tank CPU performance.

We use two date parameters in our analysis, set relative to the start and end of the previous month, which are then mapped to date parameters in the dataset to be used in the WHERE clause.

Everything was working fine as of about 21 hours ago, and there is no problem with dashboards that use SPICE datasets.

4

@Liam sorry to hear that, if you change the default value to use Exact date the issue goes away. They still haven’t fixed this yet, so going to be using that as a temporary measure

1 Like
5

Got a confirmation from AWS Support that they fixed it and related to a recent deployment. Tested and working fine now. @Koushik_Muthanna would it be possible to implement some unit tests for these cases to avoid these downtimes?

1 Like