Companies / Sigma Computing / incidents

Sigma Computing: Snowflake Tables Showing No data within Sigma but have a non-zero Row Count in Summary and Sigma SQL returns rows in Snowflake.

Impact: noneStatus: postmortemStarted Resolved (42 h)10 updatesSource: stspg.io (opens in new tab)

Affected components: AWS - Sigma - AWS (US)Sigma - AWS (US)GCP - Sigma - GCP (US)Sigma - GCP (US)Azure - Sigma - Azure (US)Sigma - Azure (US)AWS - Sigma - AWS (Europe)Sigma - AWS (Europe)AWS - Sigma - AWS (Canada)Sigma - AWS (Canada)

Timeline of updates

  1. identified

    We are currently investigating an issue that’s occurring for a small number of Snowflake customers where Tables are showing No Data but have the non-zero row count in the Summary. This issue is being treated with the highest priority and we will update the status accordingly. User Experience: Workbook elements are showing No Data and their source connection table is showing No Data but has row count in the Summary. Sigma SQL however returns results when run directly within Snowflake. Impacted Cloud Regions & Services: Sigma organizations hosted across Clouds. Incident Start Time: Approximately 3:40 UTC Aug 29, 2023

  2. identified

    Engineering is continuing to investigate this issue, which we have isolated to the fetching of results from Snowflake. We are engaging with Snowflake Engineering to look into possible changes which might explain why results are not fetching as expected.

  3. identified

    Our engineering team is actively investigating the Snowflake driver interface, focusing on analyzing Snowflake responses and checking driver version compatibility. Thank you for your patience and understanding as we work through this matter. We are committed to swiftly resolving this issue and will keep you informed about the progress. If you have any immediate concerns or questions, please feel free to reach out to our support team.

  4. identified

    Engineering has found what appear to be incomplete payloads being returned from the Snowflake data warehouse for the impacted customers. We believe this may be a result of a change that might have happened in the Snowflake environment and continue to work with Snowflake to root cause and identify a fix.

  5. identified

    Engineering is actively working on incorporating the most recent Snowflake driver code into Sigma, aiming for it to handle the variation in payload format we are observing for impacted customers.

  6. identified

    We're in direct collaboration with Snowflake to address this critical issue. Additionally, we're conducting thorough investigations on our end as we haven't ruled out the possibility of this being an issue within our code. Rest assured, we're leaving no stone unturned as we explore both avenues for a swift resolution. Your patience is greatly appreciated.

  7. monitoring

    Snowflake has acknowledged the issue and has rolled back the server changes for one of the affected customers. We're awaiting the rollback for the other affected customers. We'll keep you updated on our progress.

  8. monitoring

    Snowflake has rolled back the changes for Impacted Customers and we have heard back that the issue is now resolved for our Impacted Customers. We are continuing to monitor the situation.

  9. resolved

    The Snowflake rollback has proven effective and the issue is resolved. Impacted Customers are no longer seeing the issue. Incident Start Time: Approximately 3:40 UTC Aug 29, 2023 Incident End Time: Approximately 03:26 UTC Aug 31, 2023 We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days. You will receive a notification when that occurs.

  10. postmortem

    Sigma Engineering has completed the postmortem of this incident. A Root Cause Analysis \(RCA\) is available on the Sigma Community site: [Post Mortem for Aug 29, 2023: Tables sourced from Snowflake appeared empty, displaying “No Data” message.](https://community.sigmacomputing.com/t/post-mortem-for-aug-29-2023-tables-sourced-from-snowflake-appeared-empty-displaying-no-data-message/2578)

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Sigma Computing profile · Recent Sigma Computing incidents · Markdown · JSON