Seesaw incident
Customer Conversations Not Successfully Migrated to Messages
Seesaw experienced a minor incident on June 10, 2022 affecting Seesaw, lasting 3h 17m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 10, 2022, 03:02 PM UTC
We’re investigating an issue where some schools are reporting that they are missing their previous conversations after turning on messages. We’ve identified the root cause (a recent infrastructure upgrade) and will be fixing this ASAP, then remigrating conversations for all impacted customers. For customers that experience this, none of their conversation data is missing or lost, and we will be properly migrating previous conversations over as soon as possible. Customers can continue using messages without any impact to previous conversations.
- monitoring Jun 10, 2022, 03:38 PM UTC
We've fixed the root cause so we expect this issue should not impact any customers moving forward. We are now re-migrating the conversations for all previously impacted schools.
- monitoring Jun 10, 2022, 05:57 PM UTC
We have re-migrated the conversations for all impacted schools and are monitoring to make sure everything is fixed.
- resolved Jun 10, 2022, 06:19 PM UTC
This issue has been fully resolved and all impacted customers should now see their previous conversations in the new messaging experience.