Skip to content

Incident detail

Sisense for Cloud Data Teams Cache Clusters returning ST003 Errors

Resolved incidentMajor1 affected service

Timeline window

to

Get alerted the next time Sisense breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    Certain queries, caching, view materialization processes are running into ST003 errors. While the number of customers impacted is low, customers with the Redshift caching infrastructure are most affected. Engineers are actively working with AWS to resolve the issue. The Support Team can be reached at supportdt@sisense.com

  2. Investigating

    We are continuing to investigate this issue.

  3. Investigating

    We are continuing to investigate this issue.

  4. Investigating

    Sisense for Cloud Data Teams Engineers have diagnosed the issue to be related to the AWS outage (https://status.aws.amazon.com). Engineering are actively working to resolve the issues. The Sisense Cloud Support Team can be reached at supportdt@sisense.com or via live chat.

  5. Investigating

    Sisense for Cloud Data Teams Engineers have diagnosed the issue to be related to the AWS outage (https://status.aws.amazon.com). Engineering are actively working to resolve the issues. The Sisense Cloud Support Team can be reached at supportdt@sisense.com or via live chat.

  6. Investigating

    The engineering team is actively monitoring the issues while AWS services are being restored

  7. Identified

    The engineering team is actively monitoring the issues while AWS services are being restored

  8. Identified

    The engineering team is actively monitoring the issues while AWS services are being restored

  9. Identified

    The engineering team is actively monitoring the issues while AWS services are being restored

  10. Identified

    The number of affected customers is decreased. The engineering team is actively monitoring the issues while AWS services are being restored

  11. Identified

    The engineering team is actively monitoring the issues while AWS services are being restored

  12. Identified

    Most of the customers should be able to start using cache. If the problem persists, The Sisense Cloud Support Team can be reached at supportdt@sisense.com or via live chat. Meanwhile our Engineering team is working with AWS to restore the operations for all the customers.

  13. Identified

    The engineering team is actively monitoring the issues while AWS services are being restored

  14. Identified

    The engineering team is actively monitoring the issues while AWS services are being restored

  15. Monitoring

    We are continuing to monitor the issue as AWS works towards full recovery of Redshift clusters in the the US-East-1 region.

    Complete recovery will likely be reliant on the full recovery for the EC2 / EBS issue being tracked on the Service Health Dashboard (https://status.aws.amazon.com/ ).

    In some cases our Engineering team was able to recover the Redshift cluster on our own and are actively working through those instances of impacted clusters

    The Sisense Cloud Support Team can be reached at supportdt@sisense.com or via live chat.

  16. Monitoring

    All Redshift Operations should be restored. In case of opposite contact Sisense, Cloud Support Team can be reached at supportdt@sisense.com or via live chat.

  17. Resolved

    All Redshift Operations should be restored. In case of opposite contact Sisense, Cloud Support Team can be reached at supportdt@sisense.com or via live chat.

Keep exploring

More from Sisense

Neighboring incidents on Sisense's timeline and the rest of their record on OutageDeck.