# Agentforce, Customer360Audiences Degradation on USA1, USA2S, USA3S, USA80S… - Provider: [Salesforce](https://down.guide/salesforce) - Level: confirmed - Impact: Degraded - lasted 1d 15h - started 2026-10-06 06:00 UTC - Agentforce, Customer360Audiences - usa1, usa2s, usa3s, usa80s - id: DWN-25567c3235 - Official page: https://status.salesforce.com/incidents/20004471 ## Updates from Salesforce ### 2026-10-06 10:22 UTC: 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. ### 2026-10-06 10:41 UTC: 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. ### 2026-10-06 10:55 UTC: 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. ### 2026-10-06 15:27 UTC: 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. ### 2026-10-06 15:58 UTC: update We’re continuing the process to clear the affected data and restore normal service. In the meantime, we've also published a Known Issue article containing workaround steps that affected customers can follow to view the impacted records. Known Issue Article: https://help.salesforce.com/s/issue?id=a02g700000BAWcz We'll provide another update as additional information becomes available. ### 2026-10-07 02:41 UTC: update We’re continuing our efforts to clear the affected data to restore normal service. The data refresh is nearly complete and we are still clearing cached data that can cause errors. Some customers may still see intermittent errors when viewing Data Lake Objects until the cleanup completes. The Known Issue article remains available with workaround steps: https://help.salesforce.com/s/issue?id=a02g700000BAWcz We’ll continue monitoring the recovery and share further updates as progress is made. ### 2026-10-07 08:38 UTC: update The metadata refresh in lakehouse is complete. We’re continuing to make steady progress with clearing the cached metadata. We’re running this process at a measured pace to protect the service for all customers. Some customers may still see intermittent errors when viewing Data Lake Objects until the cleanup finishes. We’ll continue monitoring and share further updates as progress continues. ### 2026-10-07 12:11 UTC: update The metadata refresh in lakehouse is complete. We’re continuing to make steady progress with clearing cached metadata. We’re running this process at a measured pace to protect service for all customers. Some customers may still see intermittent errors when viewing Data Lake Objects until the cleanup finishes. We’ll continue monitoring and share further updates as progress continues. ### 2026-10-07 17:13 UTC: impactradiusincrease Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward. ### 2026-10-07 21:56 UTC: update The cached metadata has now been cleared. After a period of monitoring, we have confirmed that access to Data Lake Objects is restored for all affected customers. We apologize for the impact on our customers and their businesses. A full investigation will determine the technical trigger and underlying cause, and how we prevent this from happening again. --- down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).