Salesforce incident

We’ve become aware that a subset of customers are continuing to experience errors when viewing certain records within Salesforce. We've identified the trigger as stale cached data remaining from the earlier issue and are running a process to clear the affected data and restore normal service. This process is expected to take a few hours to complete. We'll provide another update as additional information becomes available. Upon further investigation, we’ve determined that the end time of the impact is different than initially understood. We’ve revised the end time of the Trust post to more accurately reflect when the issue was resolved for customers.  We apologize for any confusion. We’ve confirmed that restarting the affected components resolved the issue. Data 360 services are now working as expected including access to Data Lake Object (DLO) and Data Model Object (DMO) data in Query Editor. Our investigation also confirmed that the impact was broader than initially identified and we have updated this incident to reflect the full scope of the impact. We apologize for how this incident affected you and your business. We're investigating an issue affecting Data 360 where a subset of customers running SQL queries against their data in Data 360 may experience errors or delays. Customers are also unable to view Data Lake Object (DLO) and Data Model Object (DMO) data in Query Editor. We have restarted the affected components and are monitoring the services. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: We’ve become aware that a subset of customers are continuing to experience errors when viewing certain records within Salesforce. We've identified the trigger as stale cached data remaining from the earlier issue and are running a process to clear the affected data and restore normal service. This process is expected to take a few hours to complete. We'll provide another update as additional information becomes available. Update: Upon further investigation, we’ve determined that the end time of the impact is different than initially understood. We’ve revised the end time of the Trust post to more accurately reflect when the issue was resolved for customers.  We apologize for any confusion. Update: We’ve confirmed that restarting the affected components resolved the issue. Data 360 services are now working as expected including access to Data Lake Object (DLO) and Data Model Object (DMO) data in Query Editor. Our investigation also confirmed that the impact was broader than initially identified and we have updated this incident to reflect the full scope of the impact. We apologize for how this incident affected you and your business. Update: We're investigating an issue affecting Data 360 where a subset of customers running SQL queries against their data in Data 360 may experience errors or delays. Customers are also unable to view Data Lake Object (DLO) and Data Model Object (DMO) data in Query Editor. We have restarted the affected components and are monitoring the services. We'll provide an update in 30 minutes or sooner if additional information becomes available.