The Salesforce Technology team has observed that instance stability and performance are now at expected levels and declared the incident resolved. We will thoroughly investigate the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Update: The Salesforce Technology team has observed that instance stability and performance are now at expected levels and declared the incident resolved. We will thoroughly investigate the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information. Update: We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.

Rollback has been completed and customers using chatbots, custom agents, or Salesforce agents connecting through the Salesforce MCP Server, are no longer experiencing errors when their agent tries to query or update data in a Salesforce org. We'll perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident. Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this. We're rolling back the change that was identified as the likely trigger. Initial results confirm that connections are succeeding‌. We’re monitoring the progress of the rollback to full completion before confirming resolution. We'll provide an update in 30 minutes or sooner if additional information becomes available. We're investigating an issue affecting some customers using chatbots or custom agents connected through the Salesforce Platform Model Context Protocol (MCP) Server. Customers are experiencing errors when their agent tries to query or update data in a Salesforce org. Initial investigations indicate a recent release as the likely trigger. We're planning to roll back to the last known good version. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: Rollback has been completed and customers using chatbots, custom agents, or Salesforce agents connecting through the Salesforce MCP Server, are no longer experiencing errors when their agent tries to query or update data in a Salesforce org. We'll perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident. Update: Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this. Update: We're rolling back the change that was identified as the likely trigger. Initial results confirm that connections are succeeding‌. We’re monitoring the progress of the rollback to full completion before confirming resolution. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: We're investigating an issue affecting some customers using chatbots or custom agents connected through the Salesforce Platform Model Context Protocol (MCP) Server. Customers are experiencing errors when their agent tries to query or update data in a Salesforce org. Initial investigations indicate a recent release as the likely trigger. We're planning to roll back to the last known good version. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We’ve completed the site switch and, after a period of monitoring, can confirm that services have been restored with an out of impact time of 00:22 UTC, August 21. This is the final update for this incident. We are preparing to undertake a site switch that is expected to be the quickest way for us to restore services for customers. We can’t currently indicate how long this will take at this stage, but we will provide an update as soon as we have more information. We will provide an update in 30 minutes or sooner if new information becomes available. Upon further investigation, we believe this instance is now experiencing a service disruption as of 23:41 UTC, where users will have no access to Salesforce services hosted on the CS246 instance. We continue to actively work to fully understand the technical trigger. We will provide an update in 30 minutes or sooner if additional information becomes available. We are aware of an issue affecting the availability of certain services on instance CS246. Some customers may be unable to access affected services or may experience delays, timeouts or slow load times. Our technical teams are actively investigating the cause and working toward a resolution. We will provide an update in 30 minutes or sooner if additional information becomes available. Update: We’ve completed the site switch and, after a period of monitoring, can confirm that services have been restored with an out of impact time of 00:22 UTC, August 21. This is the final update for this incident. Update: We are preparing to undertake a site switch that is expected to be the quickest way for us to restore services for customers. We can’t currently indicate how long this will take at this stage, but we will provide an update as soon as we have more information. We will provide an update in 30 minutes or sooner if new information becomes available. Update: Upon further investigation, we believe this instance is now experiencing a service disruption as of 23:41 UTC, where users will have no access to Salesforce services hosted on the CS246 instance. We continue to actively work to fully understand the technical trigger. We will provide an update in 30 minutes or sooner if additional information becomes available. Update: We are aware of an issue affecting the availability of certain services on instance CS246. Some customers may be unable to access affected services or may experience delays, timeouts or slow load times. Our technical teams are actively investigating the cause and working toward a resolution. We will provide an update in 30 minutes or sooner if additional information becomes available.

We’ve resolved the issue affecting Revenue Cloud. We applied the remediation across affected environments, restoring functionality for customers who experienced 400 errors when performing actions such as quoting, ordering, and configuring products. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We’ve applied the remediation across the affected environments, and monitoring indicates that Revenue Cloud functionality is returning to normal. Customers may begin to see functionality restored and improvements in their experience as the remediation takes effect. We’re completing remediation in additional environments as a precautionary measure and continuing to monitor and validate recovery. We'll provide an update in 30 minutes or sooner if additional information becomes available. The configuration change we validated is restoring Revenue Cloud functionality, and we’ve now applied the remediation across multiple affected environments. We’re continuing remediation efforts across the remaining environments while monitoring recovery. We'll provide an update in 60 minutes or sooner if additional information becomes available. We've successfully validated a configuration change that resolved the errors affecting Revenue Cloud functionality in a test environment. We're now applying this change across the remaining affected environments, with recovery progressing as the remediation is completed. We'll provide an update in 30 minutes or sooner if additional information becomes available. Our investigation has identified a recent deployment to a related service as the likely trigger of the Revenue Cloud issue. We're preparing changes to restore the previous configuration across affected environments and are validating the remediation approach before proceeding. We'll provide an update in 30 minutes or sooner if additional information becomes available. Reverting the configuration change didn't resolve the issue. However, we've identified another recent change that aligns with the start of the impact and are deploying an update on an affected environment to validate whether it restores Revenue Cloud functionality. We'll provide an update in 30 minutes or sooner if additional information becomes available. We're testing changes to the configuration identified in our investigation to determine whether they restore affected Revenue Cloud functionality. In parallel, we're continuing to investigate other configuration changes that align with the start of the impact. We'll provide an update in 30 minutes or sooner if additional information becomes available. Our investigation has highlighted that a recent configuration change seems to align with the start time of the impact. We're currently focused on testing if reverting the configuration change resolves the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available. The rollback of the recent release on a test instance has been completed. However,‌ the issue still persists. We're continuing to work with additional teams to check whether a recent configuration changes may instead be the trigger of the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available. We’ve run into issues performing the rollback on test instances and are attempting to workaround these issues. Additional teams have joined the investigation and are analyzing whether their configurations may have resulted in the issue experienced by customers. We’ll provide an update in 30 minutes or sooner if additional information becomes available. We’re examining whether a separate configuration issue may be the trigger of the issue. The rollback of the recent change is still underway and we're continuing to monitor it’s progress. We've also determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We’ll provide an update in 30 minutes or sooner if additional information becomes available. We’re continuing to monitor the rollback of the recent release on the test instance. In parallel, we are investigating whether there are other actions that can be taken to bring customers out of impact, and additional teams are being engaged. We’ll provide an update in 30 minutes or sooner if additional information becomes available. The rollback of the recent release on a test instance is still underway. We're continuing to monitor the progress. If this proves successful, the release will be rolled back in all instances which received it. Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that haven't experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused. We’ll provide an update in 30 minutes or sooner if additional information becomes available. We've identified a recent release which may be the trigger of the issue. We're in the process of rolling back the release on a test instance to see if this resolves the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available. We’re investigating a feature degradation impacting Revenue Cloud. Customers may receive 400 errors when performing actions such as quoting, ordering and configuring products. We're continuing to narrow down the scope of impact and will update our messaging to reflect this as we learn more. We're engaging additional teams, and we’ll provide an update in 30 minutes or sooner if additional information becomes available. Update: We’ve resolved the issue affecting Revenue Cloud. We applied the remediation across affected environments, restoring functionality for customers who experienced 400 errors when performing actions such as quoting, ordering, and configuring products. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Update: We’ve applied the remediation across the affected environments, and monitoring indicates that Revenue Cloud functionality is returning to normal. Customers may begin to see functionality restored and improvements in their experience as the remediation takes effect. We’re completing remediation in additional environments as a precautionary measure and continuing to monitor and validate recovery. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: The configuration change we validated is restoring Revenue Cloud functionality, and we’ve now applied the remediation across multiple affected environments. We’re continuing remediation efforts across the remaining environments while monitoring recovery. We'll provide an update in 60 minutes or sooner if additional information becomes available. Update: We've successfully validated a configuration change that resolved the errors affecting Revenue Cloud functionality in a test environment. We're now applying this change across the remaining affected environments, with recovery progressing as the remediation is completed. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: Our investigation has identified a recent deployment to a related service as the likely trigger of the Revenue Cloud issue. We're preparing changes to restore the previous configuration across affected environments and are validating the remediation approach before proceeding. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: Reverting the configuration change didn't resolve the issue. However, we've identified another recent change that aligns with the start of the impact and are deploying an update on an affected environment to validate whether it restores Revenue Cloud functionality. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: We're testing changes to the configuration identified in our investigation to determine whether they restore affected Revenue Cloud functionality. In parallel, we're continuing to investigate other configuration changes that align with the start of the impact. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: Our investigation has highlighted that a recent configuration change seems to align with the start time of the impact. We're currently focused on testing if reverting the configuration change resolves the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Update: The rollback of the recent release on a test instance has been completed. However,‌ the issue still persists. We're continuing to work with additional teams to check whether a recent configuration changes may instead be the trigger of the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Update: We’ve run into issues performing the rollback on test instances and are attempting to workaround these issues. Additional teams have joined the investigation and are analyzing whether their configurations may have resulted in the issue experienced by customers. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Update: We’re examining whether a separate configuration issue may be the trigger of the issue. The rollback of the recent change is still underway and we're continuing to monitor it’s progress. We've also determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Update: We’re continuing to monitor the rollback of the recent release on the test instance. In parallel, we are investigating whether there are other actions that can be taken to bring customers out of impact, and additional teams are being engaged. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Update: The rollback of the recent release on a test instance is still underway. We're continuing to monitor the progress. If this proves successful, the release will be rolled back in all instances which received it. Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that haven't experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Update: We've identified a recent release which may be the trigger of the issue. We're in the process of rolling back the release on a test instance to see if this resolves the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Update: We’re investigating a feature degradation impacting Revenue Cloud. Customers may receive 400 errors when performing actions such as quoting, ordering and configuring products. We're continuing to narrow down the scope of impact and will update our messaging to reflect this as we learn more. We're engaging additional teams, and we’ll provide an update in 30 minutes or sooner if additional information becomes available.

Some customers experienced intermittent login failures due to elevated latency and error rates on an authentication service. The issue has been resolved after removing an internal routing rule and halting an in-progress update. Affected systems have returned to normal operating performance. We apologize for any inconvenience this incident has caused to our customers. Update: Some customers experienced intermittent login failures due to elevated latency and error rates on an authentication service. The issue has been resolved after removing an internal routing rule and halting an in-progress update. Affected systems have returned to normal operating performance. We apologize for any inconvenience this incident has caused to our customers.

Private Connect

We’ve resolved the issue affecting sandbox patching and pipeline deployments in MuleSoft Private Spaces. We completed remediation across the affected environments and confirmed that all impacted Private Spaces have returned to a healthy state. Running applications remained unaffected throughout the incident. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We continue to restore affected MuleSoft Private Spaces using the validated recovery method, with environments returning to a healthy state as remediation progresses. In parallel, we're also working with our third-party infrastructure provider on additional changes to prevent recurrence. Running applications remain unaffected, while sandbox patching and pipeline deployments may continue to be impacted in affected Private Spaces. We'll provide an update in 90 minutes, or sooner if additional information becomes available. We continue to apply the validated recovery method to affected MuleSoft Private Spaces, with environments returning to a healthy state as remediation progresses. We're also working with our third-party infrastructure provider to address the network-related issue and prevent additional impact. Running applications remain unaffected, while sandbox patching and pipeline deployments may continue to be impacted in affected Private Spaces. We'll provide an update in 90 minutes, or sooner if additional information becomes available. We successfully validated a recovery method and are applying it to the remaining affected environments. In parallel, we're continuing to work with our third-party infrastructure provider to address the underlying service limitation and prevent additional impact. Running applications remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available. We identified the technical trigger as a third-party service limitation. We're working with our third-party infrastructure provider to implement changes needed to restore the affected environments and resume pending upgrades. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available. We continue to investigate the issue affecting sandbox patching and pipeline deployments in a subset of MuleSoft Private Spaces. Our teams are working with our third-party infrastructure provider to further investigate the network connectivity issues and determine the path to recovery. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available. We continue to investigate the sandbox patching issue affecting Private Spaces. The impact radius has now increased to approximately 70 spaces across the EU and US. Node restarts proved ineffective and have been discontinued. We now believe a network configuration change in a recent platform release is the likely trigger. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available. We continue to investigate the MuleSoft sandbox patching issue affecting a subset of private spaces. One impacted space was recovered via a node restart, and we're validating this fix across all other impacted spaces. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available. We're aware of an issue affecting MuleSoft sandbox environments in a subset of private spaces across the EU and US. Approximately 42 private spaces are currently degraded, blocking customer sandbox patching and pipeline deployments. Running applications and production environments aren't impacted. We've paused further patching to prevent additional impact and are actively investigating a fix. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: We’ve resolved the issue affecting sandbox patching and pipeline deployments in MuleSoft Private Spaces. We completed remediation across the affected environments and confirmed that all impacted Private Spaces have returned to a healthy state. Running applications remained unaffected throughout the incident. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Update: We continue to restore affected MuleSoft Private Spaces using the validated recovery method, with environments returning to a healthy state as remediation progresses. In parallel, we're also working with our third-party infrastructure provider on additional changes to prevent recurrence. Running applications remain unaffected, while sandbox patching and pipeline deployments may continue to be impacted in affected Private Spaces. We'll provide an update in 90 minutes, or sooner if additional information becomes available. Update: We continue to apply the validated recovery method to affected MuleSoft Private Spaces, with environments returning to a healthy state as remediation progresses. We're also working with our third-party infrastructure provider to address the network-related issue and prevent additional impact. Running applications remain unaffected, while sandbox patching and pipeline deployments may continue to be impacted in affected Private Spaces. We'll provide an update in 90 minutes, or sooner if additional information becomes available. Update: We successfully validated a recovery method and are applying it to the remaining affected environments. In parallel, we're continuing to work with our third-party infrastructure provider to address the underlying service limitation and prevent additional impact. Running applications remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available. Update: We identified the technical trigger as a third-party service limitation. We're working with our third-party infrastructure provider to implement changes needed to restore the affected environments and resume pending upgrades. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available. Update: We continue to investigate the issue affecting sandbox patching and pipeline deployments in a subset of MuleSoft Private Spaces. Our teams are working with our third-party infrastructure provider to further investigate the network connectivity issues and determine the path to recovery. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available. Update: We continue to investigate the sandbox patching issue affecting Private Spaces. The impact radius has now increased to approximately 70 spaces across the EU and US. Node restarts proved ineffective and have been discontinued. We now believe a network configuration change in a recent platform release is the likely trigger. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available. Update: We continue to investigate the MuleSoft sandbox patching issue affecting a subset of private spaces. One impacted space was recovered via a node restart, and we're validating this fix across all other impacted spaces. Running applications and production environments remain unaffected. We'll provide an update in 60 minutes, or sooner if additional information becomes available. Update: We're aware of an issue affecting MuleSoft sandbox environments in a subset of private spaces across the EU and US. Approximately 42 private spaces are currently degraded, blocking customer sandbox patching and pipeline deployments. Running applications and production environments aren't impacted. We've paused further patching to prevent additional impact and are actively investigating a fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We confirm that email send functionality is stable. The issue was traced to a service account, which has been restored. Testing also confirms that inbound email delivery is functioning as expected. Some customers may need to retry emails that failed to send during the disruption. We apologize for the inconvenience caused by this incident and appreciate your patience while our teams worked to restore service and confirm stability. We've restored services on the impacted email infrastructure and we're validating email sending functionality before confirming full resolution. Some customers may continue to experience delivery delays during validation phase. We'll provide another update within 30 minutes, or sooner if additional information becomes available. We're aware that some customers may be experiencing intermittent issues sending email. The issue was triggered during maintenance activity on our email infrastructure. We've identified the trigger and are actively working to restore full email send functionality. We'll provide another update within 30 minutes, or sooner if there's new information. Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this. Update: We confirm that email send functionality is stable. The issue was traced to a service account, which has been restored. Testing also confirms that inbound email delivery is functioning as expected. Some customers may need to retry emails that failed to send during the disruption. We apologize for the inconvenience caused by this incident and appreciate your patience while our teams worked to restore service and confirm stability. Update: We've restored services on the impacted email infrastructure and we're validating email sending functionality before confirming full resolution. Some customers may continue to experience delivery delays during validation phase. We'll provide another update within 30 minutes, or sooner if additional information becomes available. Update: We're aware that some customers may be experiencing intermittent issues sending email. The issue was triggered during maintenance activity on our email infrastructure. We've identified the trigger and are actively working to restore full email send functionality. We'll provide another update within 30 minutes, or sooner if there's new information. Update: Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.

We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information. We’ve confirmed that the solution implemented to mitigate the issue causing the feature disruption was successful. Engineers have observed that the service is stable and have resolved the incident. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident. We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information. We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information. We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information. We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information. We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information. Update: We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information. Update: We’ve confirmed that the solution implemented to mitigate the issue causing the feature disruption was successful. Engineers have observed that the service is stable and have resolved the incident. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident. Update: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information. Update: We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.

The Salesforce Technology team has observed that instance stability and performance are now at expected levels and declared the incident resolved. We will thoroughly investigate the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We've begun deploying the corrected configuration and are validating the update before proceeding with a broader rollout. Customers may continue to experience Data 360 provisioning failures in sandbox environments while this work is underway. We'll provide an update in 90 minutes or sooner if additional information becomes available. We continue working to resolve Data 360 provisioning failures in sandbox environments by deploying an update with a corrected configuration based on a previously stable version. We'll provide an update in 60 minutes or sooner if additional information becomes available. We're now pursuing an alternative fix, deploying an update with a corrected configuration. We'll provide an update on this in 60 minutes or sooner if additional information becomes available. The most recent attempt to revert the configuration change didn't complete successfully and we're investigating a new strategy. We'll provide an update in 30 minutes or sooner if additional information becomes available. We're nearing completion of actions to revert the recent configuration change we identified as the trigger for Data 360 provisioning failures in sandbox environments. We'll provide an update in 30 minutes or sooner if additional information becomes available. We're continuing actions to revert the recent configuration change we identified as the trigger for Data 360 provisioning failures in sandbox environments. We'll provide an update in 30 minutes or sooner if additional information becomes available. Customers may continue to experience failures when attempting to provision Data 360 in sandbox environments while we work on resolving the build failure blocking the rollback. The changes needed to revert the recent configuration are approved and in progress. In parallel, we've also identified ‌the last known good version to use as a fallback if needed. We'll provide an update in 30 minutes or sooner if additional information becomes available. The rollback of the recent change is blocked because the build checks are repeatedly failing. We're engaging additional teams to work on alternate measures to resolve ‌build failures. We'll provide an update in 30 minutes or sooner if additional information becomes available. Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused. We're investigating an issue impacting Data 360 provisioning in sandbox environments. Customers may experience failures when attempting to provision Data 360. Initial investigations indicate a recent configuration change that didn't complete successfully as the likely trigger. We're evaluating a rollback of that change in a test environment to confirm it resolves the failures. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: The Salesforce Technology team has observed that instance stability and performance are now at expected levels and declared the incident resolved. We will thoroughly investigate the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Update: We've begun deploying the corrected configuration and are validating the update before proceeding with a broader rollout. Customers may continue to experience Data 360 provisioning failures in sandbox environments while this work is underway. We'll provide an update in 90 minutes or sooner if additional information becomes available. Update: We continue working to resolve Data 360 provisioning failures in sandbox environments by deploying an update with a corrected configuration based on a previously stable version. We'll provide an update in 60 minutes or sooner if additional information becomes available. Update: We're now pursuing an alternative fix, deploying an update with a corrected configuration. We'll provide an update on this in 60 minutes or sooner if additional information becomes available. Update: The most recent attempt to revert the configuration change didn't complete successfully and we're investigating a new strategy. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: We're nearing completion of actions to revert the recent configuration change we identified as the trigger for Data 360 provisioning failures in sandbox environments. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: We're continuing actions to revert the recent configuration change we identified as the trigger for Data 360 provisioning failures in sandbox environments. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: Customers may continue to experience failures when attempting to provision Data 360 in sandbox environments while we work on resolving the build failure blocking the rollback. The changes needed to revert the recent configuration are approved and in progress. In parallel, we've also identified ‌the last known good version to use as a fallback if needed. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: The rollback of the recent change is blocked because the build checks are repeatedly failing. We're engaging additional teams to work on alternate measures to resolve ‌build failures. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused. Update: We're investigating an issue impacting Data 360 provisioning in sandbox environments. Customers may experience failures when attempting to provision Data 360. Initial investigations indicate a recent configuration change that didn't complete successfully as the likely trigger. We're evaluating a rollback of that change in a test environment to confirm it resolves the failures. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Rolling restarts completed for all impacted instances at 19:54 UTC, and we have verified that the issue affecting Proactive Monitoring limit alerts has been resolved. We apologize for how you and your business may have been affected by this. We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We performed a rolling restart on a test instance and have verified that Proactive Monitoring limit alerts have been successfully restored on that instance. We are now applying the same restart across the remaining affected instances. We'll provide another update once the rolling restarts have completed, or sooner if additional information becomes available. 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. We're continuing to investigate the issue affecting Proactive Monitoring limit alerts for a subset of customers. Our investigation confirms that other monitoring data continues to process normally, and the issue remains isolated to the specific monitoring data used to generate these limit alerts. We've validated the broader monitoring pipeline and are continuing to investigate why the affected limit-monitoring data is not being generated as expected. We'll provide another update in 60 minutes or sooner if additional information becomes available. We're investigating an issue affecting Proactive Monitoring limit alerts, where some customers may not receive expected notifications. The impact is limited to customers using the affected limit monitoring functionality, and the underlying Salesforce services remain available. We've narrowed the investigation to the processing of specific monitoring data used to generate these alerts and are working to restore normal alerting functionality. We'll provide another update in 30 minutes or sooner if additional information becomes available. Update: Rolling restarts completed for all impacted instances at 19:54 UTC, and we have verified that the issue affecting Proactive Monitoring limit alerts has been resolved. We apologize for how you and your business may have been affected by this. We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Update: We performed a rolling restart on a test instance and have verified that Proactive Monitoring limit alerts have been successfully restored on that instance. We are now applying the same restart across the remaining affected instances. We'll provide another update once the rolling restarts have completed, or sooner if additional information becomes available. Update: 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. Update: We're continuing to investigate the issue affecting Proactive Monitoring limit alerts for a subset of customers. Our investigation confirms that other monitoring data continues to process normally, and the issue remains isolated to the specific monitoring data used to generate these limit alerts. We've validated the broader monitoring pipeline and are continuing to investigate why the affected limit-monitoring data is not being generated as expected. We'll provide another update in 60 minutes or sooner if additional information becomes available. Update: We're investigating an issue affecting Proactive Monitoring limit alerts, where some customers may not receive expected notifications. The impact is limited to customers using the affected limit monitoring functionality, and the underlying Salesforce services remain available. We've narrowed the investigation to the processing of specific monitoring data used to generate these alerts and are working to restore normal alerting functionality. We'll provide another update in 30 minutes or sooner if additional information becomes available.

The issue affecting the Account Manager was resolved at 17:44 UTC. We successfully transitioned traffic to the standby environment following validation, and the Account Manager has returned to normal operation. Service metrics are healthy, and the system is no longer operating in maintenance mode. We'll perform a full investigation of the incident and identify preventive actions to help avoid a recurrence. Our maintenance activity is progressing as planned. We've completed initial validation of the standby environment and are seeing expected service behavior. We are completing the remaining deployment activity and will then perform additional automated validation before transitioning traffic to the standby environment. We'll continue to monitor progress closely and provide another update in 60 minutes or sooner if additional information becomes available. We're investigating an issue affecting Account Manager where customers may experience intermittent errors. To restore service stability, we've initiated maintenance to transition Account Manager to a standby environment. During this activity, Account Manager will remain available in read-only mode, and customers may be unable to make configuration changes. We expect the maintenance activity to take approximately one hour and are closely monitoring progress. We'll provide an update in 90 minutes or sooner if additional information becomes available. 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. Update: The issue affecting the Account Manager was resolved at 17:44 UTC. We successfully transitioned traffic to the standby environment following validation, and the Account Manager has returned to normal operation. Service metrics are healthy, and the system is no longer operating in maintenance mode. We'll perform a full investigation of the incident and identify preventive actions to help avoid a recurrence. Update: Our maintenance activity is progressing as planned. We've completed initial validation of the standby environment and are seeing expected service behavior. We are completing the remaining deployment activity and will then perform additional automated validation before transitioning traffic to the standby environment. We'll continue to monitor progress closely and provide another update in 60 minutes or sooner if additional information becomes available. Update: We're investigating an issue affecting Account Manager where customers may experience intermittent errors. To restore service stability, we've initiated maintenance to transition Account Manager to a standby environment. During this activity, Account Manager will remain available in read-only mode, and customers may be unable to make configuration changes. We expect the maintenance activity to take approximately one hour and are closely monitoring progress. We'll provide an update in 90 minutes or sooner if additional information becomes available. Update: 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.

We’ve completed our investigation and determined that the issue was triggered by a known issue caused by a third-party vendor, which affected the network connection to the database. This resulted in the intermittent service disruption observed by customers. We'll continue to work alongside the vendor to ensure the issue doesn't occur again. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Work is underway to understand whether a recent change resulted in the impact that customers are intermittently experiencing. In parallel, we're investigating if an issue affecting a network connection to a database is related. We’re working to gather relevant logs. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Upon further investigation, we’ve determined that customers may see 500 errors when trying to access their Commerce Cloud services, including Storefronts. Customers may be seeing signs of recovery, however, due to the intermittent nature of the issue we’re continuing the investigation. We’re analyzing error logs to better understand the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available. We’ve identified a service disruption which is intermittently affecting customers on POD248. Customers are intermittently unable to access their Storefronts and other Commerce Cloud services such as Business Manager. We're engaging additional teams to assist with the investigation. We're also evaluating whether a recent change is the trigger of this issue. We've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Update: We’ve completed our investigation and determined that the issue was triggered by a known issue caused by a third-party vendor, which affected the network connection to the database. This resulted in the intermittent service disruption observed by customers. We'll continue to work alongside the vendor to ensure the issue doesn't occur again. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Update: Work is underway to understand whether a recent change resulted in the impact that customers are intermittently experiencing. In parallel, we're investigating if an issue affecting a network connection to a database is related. We’re working to gather relevant logs. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Update: Upon further investigation, we’ve determined that customers may see 500 errors when trying to access their Commerce Cloud services, including Storefronts. Customers may be seeing signs of recovery, however, due to the intermittent nature of the issue we’re continuing the investigation. We’re analyzing error logs to better understand the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Update: We’ve identified a service disruption which is intermittently affecting customers on POD248. Customers are intermittently unable to access their Storefronts and other Commerce Cloud services such as Business Manager. We're engaging additional teams to assist with the investigation. We're also evaluating whether a recent change is the trigger of this issue. We've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

The issue affecting some Salesforce Industries customers using OmniStudio deployment tooling was resolved as of 16:08 UTC on August 16. Customers may have experienced failures when deploying, importing, or exporting OmniStudio components between 00:01 UTC and 16:08 UTC. We restored the required supporting service and validated that normal functionality has returned. We'll perform a full investigation of the incident and identify preventive actions to help avoid a recurrence. Update: The issue affecting some Salesforce Industries customers using OmniStudio deployment tooling was resolved as of 16:08 UTC on August 16. Customers may have experienced failures when deploying, importing, or exporting OmniStudio components between 00:01 UTC and 16:08 UTC. We restored the required supporting service and validated that normal functionality has returned. We'll perform a full investigation of the incident and identify preventive actions to help avoid a recurrence.