Skip to content

Incident detail

Sisense for Cloud Data Teams Database Connection Errors

Resolved incidentMinor1 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. Monitoring

    Starting at 10:22am PST, some Sisense for Cloud Data Teams customers database connections experienced connection errors due to a recent code change. Engineers rolled back the code at 10:53am PST and are monitoring the connections. The Sisense Cloud Support Team can be reached at supportdt@sisense.com or via live chat.

  2. Monitoring

    Some Sisense for Cloud Data Teams customers database connections are still experiencing errors from the previous changes. Engineers are working to re-start those connections and will be monitoring. The Sisense Cloud Support Team can be reached at supportdt@sisense.com or via live chat.

  3. Monitoring

    Sisense for Cloud Data Teams engineers have restarted the connection services and databases are connecting as normal. The Engineers are monitoring for any further issues. The support team can be reached at supportdt@sisense.com or via live chat for further questions.

  4. Resolved

    Sisense for Cloud Data Teams engineers have resolved the underlying cause of the ST003 connection errors.

    Some users may still have lingering errors. For these users, a database admin will have to unblock the Sisense user before full functionality can be restored. Please have a database admin execute

    mysqladmin flush-hosts

    For further details, please refer to: https://dev.mysql.com/doc/refman/5.6/en/host-cache.html#host-cache-flushing

Keep exploring

More from Sisense

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