GetFeedback incident
Responses not appearing in response tables
GetFeedback experienced a notice incident on May 8, 2023 affecting Survey Builder & Administration, lasting 16d 18h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 08, 2023, 02:56 PM UTC
We are aware of clients reporting their responses no longer appearing in response table and only being available in exports. We're currently investigating the issue and will provide updates as they become available
- investigating May 08, 2023, 04:17 PM UTC
We continue to look into the issue.
- identified May 08, 2023, 05:35 PM UTC
We have found the source of the issue and are working on a fix
- identified May 08, 2023, 06:26 PM UTC
We are working to restore client data back to response tables. No data has been lost, and clients should slowly see their data populating over the course of the day. It unfortunately could take a few hours to restore all client's data, we'll provide an estimate when possible.
- investigating May 09, 2023, 01:04 PM UTC
we're aware of GetFeedback failing to load and erroring out. We're looking into the issue and will provide updates as they become available
- monitoring May 09, 2023, 01:45 PM UTC
We have found and resolved the issue involving time-out errors and load failures. Clients should be able to log in without issue. We continue to restore client data back to response tables
- monitoring May 11, 2023, 10:06 AM UTC
We continue work to restore data to clients. Response data from May 8th before 11am PT isn't viewable in app for all customers, but is available through an export and Insights. The issue is only affecting GF Direct customers in our US data center. We'd like to reiterate that no customer data was lost. We'll continue to provide updates when possible
- resolved May 25, 2023, 09:53 AM UTC
We have restored all data in app for our clients and they should have full access as of now. We will continue to monitor dashboards, and will be conducting a postmortem to ensure this issue dos not occur again