Tableau Cloud Outage History

Started Jun 03, 2026, 03:42 PM UTC· resolved Jun 03, 2026, 06:49 PM UTC

1. identified Jun 03, 2026, 03:42 PM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Jun 03, 2026, 03:55 PM UTC

   The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.

3. monitoring Jun 03, 2026, 05:46 PM UTC

   We continue to investigate an issue affecting customers using the Snowflake Data Share feature within Data 360. The fix has been successfully deployed to our ‌testing environment and is being monitored. Full deployment across all production environments remains in-progress; however, progress is currently delayed due to a secondary infrastructure issue impacting our deployment pipeline. Engineering teams are actively working to resolve this blocker. We'll provide an update within 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jun 03, 2026, 03:13 AM UTC· resolved Jun 03, 2026, 07:07 AM UTC

1. identified Jun 03, 2026, 03:13 AM UTC

   Degradation Started: performanceDegradation

2. monitoring Jun 03, 2026, 05:38 AM UTC

   We are investigating a performance degradation where a subset of users may experience slow console performance. We have identified the cause and are actively working to restore full service. We're currently restarting backend services on the affected instances to resolve the issue. Please note that the scope of impact has expanded, and we're monitoring additional instances showing similar symptoms. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jun 03, 2026, 06:00 AM UTC

   Work continues on restarting backend services on the affected instances. In parallel we are also assessing potential impacts on other instances, as well as further remediation actions. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jun 03, 2026, 06:19 AM UTC

   Investigation and restoration efforts remain ongoing. We'll provide an update in 30 minutes or sooner if additional information becomes available, and apologize for any inconvenience this is causing.

5. monitoring Jun 03, 2026, 06:48 AM UTC

   We have determined that this issue is related to resource capacity constraints on the underlying database infrastructure. To mitigate the issue we have restarted the affected database nodes. We're closely monitoring the system's performance following these restarts to evaluate their effectiveness in restoring optimal service levels. We'll provide another update in 30 minutes, or sooner if additional information becomes available.

Read the full incident report →

Started Jun 03, 2026, 03:03 AM UTC· resolved Jun 03, 2026, 04:57 AM UTC

1. identified Jun 03, 2026, 03:03 AM UTC

   Degradation Started: performanceDegradation

2. monitoring Jun 03, 2026, 03:28 AM UTC

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

3. monitoring Jun 03, 2026, 04:02 AM UTC

   We are investigating a potential cause of the issue.

Read the full incident report →

Started Jun 01, 2026, 07:32 AM UTC· resolved Jun 01, 2026, 11:19 AM UTC

1. identified Jun 01, 2026, 07:32 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Jun 01, 2026, 08:05 AM UTC

   We’re investigating intermittent failures affecting Einstein Translator through the Einstein Trust Layer that may cause internal server errors when submitting translation requests. We identified a capacity constraint as a contributing factor, and have initiated redeployment actions and refreshed impacted services to help restore service stability. We're actively monitoring service health and error rates as we continue to assess recovery. Our investigations 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 apologize for any confusion caused by this. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jun 01, 2026, 08:53 AM UTC

   Our efforts to increase capacity on the underlying model-serving infrastructure encountered deployment-related issues. We are working on pre-checks before initiating a new deployment. We will share an update once we have additional information on recovery efforts.

4. monitoring Jun 01, 2026, 10:39 AM UTC

   Further investigation identified the need to engage the vendor. We’re working with the vendor to verify whether the target infrastructure can support the planned capacity expansion and then we can re-initiate the deployment to restore the service. We will provide an update if new information becomes available.

Read the full incident report →

Started May 29, 2026, 04:52 AM UTC· resolved May 29, 2026, 08:52 AM UTC

1. identified May 29, 2026, 04:52 AM UTC

   Degradation Started: muleSoftFeatureDisruption

2. monitoring May 29, 2026, 05:29 AM UTC

   The MuleSoft CloudHub 2 and Runtime Fabric services are currently experiencing an issue that prevents customers from deploying new applications. Existing running applications are not affected. We're actively investigating the cause and exploring paths to resolution. We'll provide an update in 60 minutes or sooner if additional information becomes available.

3. monitoring May 29, 2026, 06:18 AM UTC

   We continue to investigate the issue where customers are unable to deploy new applications on CloudHub 2 and Runtime Fabric. Existing running applications remain unaffected. We have identified a recent release as the cause of this issue and are preparing to roll back the release. We'll provide an update within 60 minutes or sooner if the situation changes.

4. monitoring May 29, 2026, 07:03 AM UTC

   We continue to investigate an issue impacting MuleSoft Anypoint Platform where customers are unable to deploy new applications on CloudHub 2 and Runtime Fabric. Existing running applications remain unaffected. While preparing for the rollback the team identified customers running self-managed Flex Gateways in connected mode may experience Domain Name System (DNS) resolution failures preventing connectivity to the Anypoint Platform control plane. Existing running applications and APIs are not impacted. Our engineering team has identified a configuration change as the likely root cause and is actively working to resolve this issue. We will provide an update within 60 minutes or as soon as additional information is available.

5. monitoring May 29, 2026, 08:15 AM UTC

   A recent deployment introduced a misconfiguration in our US and EU environments, which has been identified as the likely cause of the issue. We're currently deploying a fix and monitoring the situation. We'll provide another update within 60 minutes, or sooner if additional information becomes available.

Read the full incident report →

Started May 29, 2026, 12:41 AM UTC· resolved May 29, 2026, 01:09 AM UTC

1. identified May 29, 2026, 12:41 AM UTC

   Degradation Started: performanceDegradation

2. monitoring May 29, 2026, 12:41 AM UTC

   We're aware of an issue impacting Einstein Search Analytics DLOs (Data Lake Objects). Customers who have enabled search interaction logging may find that their Einstein Search Analytics Dashboard is missing data from May 18, 2026. We've identified a release as the trigger and our teams are working to roll back to the most recent known, good release. This may take several hours to complete. We'll provide an update once we have new information available.

Read the full incident report →

Started May 28, 2026, 01:07 PM UTC· resolved May 28, 2026, 02:12 PM UTC

1. identified May 28, 2026, 01:07 PM UTC

   Degradation Started: salesforceDataCloudServiceDegradation

Read the full incident report →

Started May 28, 2026, 10:58 AM UTC· resolved May 28, 2026, 11:40 AM UTC

1. identified May 28, 2026, 10:58 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring May 28, 2026, 11:08 AM UTC

   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.

3. monitoring May 28, 2026, 11:14 AM UTC

   We're continuing to investigate an issue causing intermittent failures for customers using Einstein Translator through the Einstein Trust Layer. Affected customers may receive an internal server error when submitting translation requests. We've refreshed a number of impacted service instances and are actively monitoring error rates to assess whether this action has restored service stability. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started May 26, 2026, 12:05 AM UTC· resolved May 26, 2026, 08:31 AM UTC

1. identified May 26, 2026, 12:05 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring May 26, 2026, 12:05 AM UTC

   Update

3. monitoring May 26, 2026, 12:06 AM UTC

   We're investigating an issue affecting Agentforce. Customers may be unable to use virtual agents, or receive errors when attempting to run agentic tasks. We've engaged our technical teams to address capacity constraints on the AI inference services supporting Agentforce in the South America region, and continue to investigate the issue to try to identify the root cause. We'll provide an update in 60 minutes or sooner if additional information becomes available.

4. monitoring May 26, 2026, 12:57 AM UTC

   We’ve identified a capacity constraint on the AI inference service supporting key Agentforce features as the cause of this issue. We’ve deployed an initial fix to our production environment, which included disabling one feature as an initial mitigation measure. We're testing a second fix that will further support service restoration, and we'll deploy this to production once this has been validated. This may take several hours to complete. We'll provide an update in 60 minutes or sooner if additional information becomes available.

5. monitoring May 26, 2026, 03:53 AM UTC

   We continue to work on additional mitigation steps to restore impacted Agentforce services in the South America region. We're currently validating the planned changes before deploying them to production. Customers may continue to experience issues using virtual agents or running agentic tasks while this work is underway. We'll provide an update in 60 minutes or sooner if additional information becomes available

6. monitoring May 26, 2026, 06:03 AM UTC

   We're working to restore the Agentforce service disruption impacting customers in the South America region. We’re validating the effectiveness of planned mitigation measures before deploying the fix. We'll provide an update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 08:39 PM UTC

1. identified May 22, 2026, 06:15 PM UTC

   Degradation Started: salesforceDataCloudServiceDegradation

2. monitoring May 22, 2026, 06:19 PM UTC

   Customers using CRM Data streams in streaming mode may notice increased latency for data flowing from Salesforce Platform into Data Cloud.

Read the full incident report →

Started May 21, 2026, 10:02 PM UTC· resolved May 22, 2026, 02:56 AM UTC

1. identified May 21, 2026, 10:02 PM UTC

   Disruption Started: serviceDisruption

2. monitoring May 21, 2026, 10:02 PM UTC

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

3. monitoring May 21, 2026, 10:30 PM UTC

   At 20:00 UTC on May 21, 2026, a feature disruption began impacting the Salesforce Core Service in the NA223 instance. As a result, customers may be experiencing intermittent disruptions and degradations due to instability. We are engaged and are actively analyzing the issue to determine a mitigation pathway. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring May 21, 2026, 11:15 PM UTC

   We’ve identified a recent networking patch as the potential trigger. Some customers attempting to log in via login.salesforce.com or test.salesforce.com may be experiencing issues. We’ve initiated a reboot of impacted networking hosts as a possible solution. The team continues to analyze the trigger and explore additional remediation pathways. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring May 21, 2026, 11:16 PM UTC

   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.

6. monitoring May 22, 2026, 12:37 AM UTC

   Our investigations have highlighted that the impact radius is broader than initially understood. Please refer to https://status.salesforce.com/generalmessages/20000254 for all further communications about this issue. We sincerely apologise for how this issue has impacted you and your business.

Read the full incident report →

Started May 21, 2026, 04:11 PM UTC· resolved May 22, 2026, 03:43 AM UTC

1. identified May 21, 2026, 04:11 PM UTC

   Degradation Started: performanceDegradation

2. monitoring May 21, 2026, 04:11 PM UTC

   At 07:00 UTC, we noted a performance degradation impacting Apex test executions in some sandbox environments. At this time, some customers using SOQL queries with filters on External ID fields may experience test class failures due to no rows being returned during test execution. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring May 21, 2026, 04:54 PM UTC

   We continue to investigate the issue impacting Apex test executions in some sandbox environments. Our engineering teams have identified a technical trigger and have developed a potential fix, which is currently undergoing validations. Once complete, we'll perform an expedited deployment to all impacted instances. We will provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring May 21, 2026, 05:34 PM UTC

   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.

5. monitoring May 21, 2026, 05:36 PM UTC

   We continue to investigate the issue impacting Apex test executions in some sandbox environments. Ongoing validations of the current fix has shown some success, however we have also identified a potential regression. We are investigating this further to identify the cause. We will provide an update in 60 minutes or sooner if additional information becomes available.

6. monitoring May 21, 2026, 06:32 PM UTC

   We continue to investigate the issue impacting Apex test executions in some sandbox environments. Ongoing investigation of the regression has identified additional changes which need to be reverted to its last known good configuration. The potential fix is currently underway and we will validate remediation once it's complete. We will provide an update in 60 minutes or sooner if additional information becomes available.

7. monitoring May 21, 2026, 07:43 PM UTC

   We continue to investigate the issue impacting Apex test executions in some sandbox environments. The identified additional changes have been reverted to their last known good configuration, but impact still persists. We are investigating the issue and potential remediation solutions. We will provide an update in 60 minutes or sooner if additional information becomes available.

8. monitoring May 21, 2026, 09:03 PM UTC

   We are currently deep-diving into system logs, attempting to reproduce the issue in isolation, and evaluating additional remediation options, including app server restart across all sandbox environments. We will provide an update in 60 minutes or sooner if additional information becomes available.

9. monitoring May 21, 2026, 09:59 PM UTC

   We have completed a rolling restart of application servers to clear cached connection states; however, some customers continue to experience Apex test failures. We are actively collecting database traces and reviewing logs to determine the underlying technical cause and identify next steps. We will provide an update in 60 minutes or sooner if additional information becomes available.

10. monitoring May 21, 2026, 11:13 PM UTC

    Further investigation indicates the continued customer failures are not related to this issue. The rolling restarts successfully released connections with pre-mitigation configurations. We are currently performing final validations and taking proactive actions to ensure full remediation. Some customers may observe Apex test executions are now succeeding. We will provide an update in 60 minutes or sooner if additional information becomes available.

11. monitoring May 22, 2026, 12:23 AM UTC

    We completed rolling restarts across the initially impacted sandbox environments and cleared the cached database connections that retained the previous configurations. Apex test executions are now succeeding for affected customers. As a proactive measure to ensure full remediation, we're currently performing a fleet-wide rolling restart across all remaining sandbox environments. We'll provide a final update upon the completion of these actions, or sooner if additional information becomes available.

Read the full incident report →

Started May 20, 2026, 08:01 PM UTC· resolved May 20, 2026, 10:05 PM UTC

1. identified May 20, 2026, 08:01 PM UTC

   Degradation Started: featurePerfDegradation

2. monitoring May 20, 2026, 08:04 PM UTC

   At approximately 16:00 UTC on May 20, 2026, we became aware of a feature degradation impacting a subset of Marketing Cloud Engagement customers. A recent deployment that manages unsubscribe link processing has introduced an issue where some unsubscribe requests may not be successfully processed. This issue specifically impacts customers on Stacks 1, 5, 6, 7, 10, and 51 who utilize custom CloudPages for their unsubscribe branding or behavior. We estimate that roughly 25% of unsubscribe links may not properly process during an unsubscribe attempt. We have identified the trigger and are currently preparing remediation steps to restore normal functionality. We will provide an update in 30 minutes, or sooner if additional information becomes available.

3. monitoring May 20, 2026, 08:26 PM UTC

   We completed the deployment of a fix to all six impacted stacks and we’ve now entered a monitoring phase to ensure the settings have fully propagated. We will begin the validation of the fix at approximately 20:30 UTC. We will provide an update in 60 minutes, or sooner if additional information becomes available.

4. monitoring May 20, 2026, 09:21 PM UTC

   During the subsequent validation phase, we identified that the fix required a configuration adjustment to fully restore functionality. We have developed a revised remediation plan and are currently in the process of merging and deploying this update to the affected environments. We expect to begin the next round of validation shortly. We will provide an update in 60 minutes, or sooner if additional information becomes available.

Read the full incident report →

Started May 20, 2026, 12:35 PM UTC· resolved May 20, 2026, 01:52 PM UTC

1. identified May 20, 2026, 12:35 PM UTC

   Degradation Started: agentforceAsaSdrFeatureDegradation

2. monitoring May 20, 2026, 01:01 PM UTC

   We're investigating an issue impacting Agentforce messaging session transfers where a subset of customers using Service Agent are observing failures resulting in 504 Upstream Request Timeout errors. We're investigating to establish further details on the potential scope of ‌impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring May 20, 2026, 01:20 PM UTC

   We have performed a rolling restart of the impacted instances and validation is in progress. Initial results are positive and we're monitoring performance to ensure there are no errors. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started May 20, 2026, 01:38 AM UTC· resolved May 20, 2026, 04:43 AM UTC

1. identified May 20, 2026, 01:38 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring May 20, 2026, 01:38 AM UTC

   At 23:50 UTC on May 19, 2026 we began investigating a feature disruption impacting Salesforce Field Service (SFS) Mobile Services. Impacted customers may receive 403 error messages when trying to use the performance priming feature. We are in the process of deploying a fix to remediate the issue and this is expected to take approximately 60 minutes. We’ll provide an update in the next 60-90 minutes or sooner if new information, or validation of the fix, becomes available.

3. monitoring May 20, 2026, 04:06 AM UTC

   We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update once the fix has been deployed and validated, or sooner if we have more information.

Read the full incident report →

Started May 19, 2026, 07:40 PM UTC· resolved May 20, 2026, 12:41 AM UTC

1. identified May 19, 2026, 07:40 PM UTC

   Degradation Started: featurePerfDegradation

2. monitoring May 19, 2026, 07:42 PM UTC

   We are aware of an issue impacting Agentforce. As a result, some users may be unable to complete Agentforce conversations or interactions. We've increased capacity across multiple services involved in Agentforce request processing as part of our remediation efforts. We're continuing to investigate and implement additional capacity increases to fully restore service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring May 19, 2026, 07:59 PM UTC

   We are seeing signs of improvement following the capacity increases across the Agentforce service tiers. We continue to monitor the stability of the environment and are validating that these remediation efforts are successfully managing increased traffic volumes. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring May 19, 2026, 08:20 PM UTC

   We have completed capacity increases across several internal services to stabilize the environment. While we are seeing signs of improvement, we continue to monitor the service as traffic volumes fluctuate. Our engineering teams are now focused on implementing additional optimizations to ensure the service remains resilient during peak usage periods. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring May 19, 2026, 08:40 PM UTC

   We continue to observe stable performance following capacity increases across Agentforce services. Our engineering teams have implemented a change to improve service resilience against high traffic volumes. While remediation efforts are showing positive results, we continue to monitor the effectiveness of these changes as traffic patterns evolve. We'll provide an update in 60 minutes or sooner if additional information becomes available.

6. monitoring May 19, 2026, 09:23 PM UTC

   We continue to see stable performance and have successfully maintained service availability for the majority of customers. Our engineering teams are finalizing additional resilience changes to ensure the environment remains stable as traffic volumes continue to increase. We are closely monitoring downstream services to ensure performance remains within optimal thresholds. We will provide further updates upon significant development.

Read the full incident report →

Started May 18, 2026, 10:27 PM UTC· resolved May 19, 2026, 01:28 AM UTC

1. identified May 18, 2026, 10:27 PM UTC

   Degradation Started: performanceDegradation

2. monitoring May 18, 2026, 10:44 PM UTC

   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.

3. monitoring May 18, 2026, 10:44 PM UTC

   At 00:49 UTC on May 16, 2026, we noted a performance degradation impacting the synchronization of email and calendar events. As a result, some customers may experience significant delays in email and calendar events syncing successfully. Initial investigation has determined the issue is related to an unintended autoscaling operation affecting specific node pools. Engineering teams are actively working to stabilize the impacted infrastructure, prevent additional scale-down activity, and restore normal processing performance. We will provide another update within 30 minutes or sooner if additional information becomes available.

4. monitoring May 18, 2026, 11:11 PM UTC

   We have implemented corrective actions to stabilize the impacted infrastructure and have mitigated high-traffic data sources contributing to the delays. While we are seeing a steady improvement in processing rates, customers with the Einstein Activity Capture (EAC) feature enabled may continue to experience delays in email and calendar event synchronization as the remaining backlog of events is processed. We are closely monitoring the service as performance levels return to normal. We will provide another update upon significant update or sooner if additional information becomes available.

Read the full incident report →

Started May 16, 2026, 12:57 PM UTC· resolved May 16, 2026, 04:36 PM UTC

1. identified May 16, 2026, 12:57 PM UTC

   Degradation Started: muleSoftPerformanceDegradation

2. monitoring May 16, 2026, 12:59 PM UTC

   At 09:30 UTC, May 16, 2026, we identified a performance degradation affecting the Secrets Manager Provider and API in our production environment. As a result, customers attempting to deploy or restart applications may be unable to do so successfully, as secrets cannot be retrieved during this process. Currently running applications that are not restarting are not impacted and will continue to operate normally. We have identified a potential technical trigger and have initiated a remediation process. We are working to restore full service and will provide an update within 30 minutes or sooner if additional information becomes available.

3. monitoring May 16, 2026, 01:28 PM UTC

   The previous attempt to restore the service didn't yield the desired results. We continue to investigate the issue and analyze data to determine the best path to resolution. We’ll provide an update upon significant update, or sooner if additional information becomes available.

4. monitoring May 16, 2026, 02:34 PM UTC

   We are working on resolving the impact on runtime manager in the US control plane. Customers using Application Manager will not be able to deploy or re-deploy their applications. We’ll provide an update upon significant update, or sooner if additional information becomes available.

5. monitoring May 16, 2026, 03:58 PM UTC

   We have successfully validated and tested the fix. Initial reports have indicated positive results and services were restored to normal operating levels for the verification instances. We are reviewing additional logs to confirm the fix. We’ll provide an update upon significant update, or sooner if additional information becomes available.

Read the full incident report →

Started May 15, 2026, 02:03 PM UTC· resolved May 15, 2026, 04:00 PM UTC

1. identified May 15, 2026, 02:03 PM UTC

   Disruption Started: ccStorefrontSAndOrBusinessManagerUnavailable

2. monitoring May 15, 2026, 02:09 PM UTC

   We're aware of an issue that we believe is impacting a subset of Commerce Cloud Storefronts. As a result, some customers are unable to access their Storefronts, and pages and prices aren't loading. We're investigating to establish further details on the potential ‌impact scope. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring May 15, 2026, 02:33 PM UTC

   We've identified a potential trigger with routing and utility infrastructure availability and are preparing a recovery plan to execute a failover for this utility. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring May 15, 2026, 02:47 PM UTC

   The failover to a healthy server is progressing well. We've completed the switch and are now completing the final steps to confirm service restoration for affected customers. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring May 15, 2026, 03:26 PM UTC

   We've completed the failover and are seeing positive initial results. We're continuing to monitor the environment closely to ensure stability. Upon further investigation, we've determined that the start time of the impact was 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.

Read the full incident report →

Started May 14, 2026, 12:31 PM UTC· resolved May 14, 2026, 02:57 PM UTC

1. identified May 14, 2026, 12:31 PM UTC

   Degradation Started: performanceDegradation

2. monitoring May 14, 2026, 12:51 PM UTC

   We’re investigating an issue causing CRM Analytics (CRMA) customer jobs to run slowly or remain stuck in the queue, resulting in stale data in CRMA dashboards. We identified the cause as a capacity migration where a required rolling restart was not performed after the capacity addition. As a result, jobs routed to the newly added pods are failing and accumulating in the queue. We are now performing the required rolling restart and monitoring job queue recovery. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring May 14, 2026, 01:27 PM UTC

   We’ve identified that this is impacting Recipes, Data flows, Data Sync and other CRMA jobs. The rolling restart is underway, and we continue to monitor the pending job queue. This will take sometime and we'll share the next update when we have progressed.

Read the full incident report →

Started May 14, 2026, 09:55 AM UTC· resolved May 15, 2026, 01:08 AM UTC

1. identified May 14, 2026, 09:55 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring May 14, 2026, 10:06 AM UTC

   We are investigating an issue impacting Commerce Cloud customers using a specific third-party payment service provider to process payments. As a result, the orders are not completing. We believe the trigger may be related to this recent release. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring May 14, 2026, 10:38 AM UTC

   We’ve analyzed further and it’s confirmed that the recent release is the cause. A rollback of this release is being discussed as to whether it involves any further disruption to the service as this involves a complex configuration change. Also, the impact radius is broader than initially understood. We have updated the posting to reflect the additional PODs experiencing impact, and customers will receive communication. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring May 14, 2026, 11:18 AM UTC

   Further investigation confirmed that SOAP API and SOAP Web Service calls to third-party payment gateways are failing, resulting in the current impact. We’re evaluating the best rollback approach while also exploring alternative mitigation options to minimize any additional risk. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring May 14, 2026, 11:36 AM UTC

   We’ve initiated a rollback on a test POD followed by application server restarts to validate the approach before extending the rollback to the remaining impacted PODs. We are closely monitoring the rollback process. We'll provide an update in 60 minutes or sooner if additional information becomes available.

6. monitoring May 14, 2026, 12:08 PM UTC

   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.

7. monitoring May 14, 2026, 12:18 PM UTC

   We're still‌ performing the rollback and application server restarts on a test POD. This is expected to take some time to complete. We're continuing to monitor it’s progress. We'll provide an update in 60 minutes or sooner if additional information becomes available.

8. monitoring May 14, 2026, 01:31 PM UTC

   The rollback on a test POD was unsuccessful. We're now‌ developing a fix in the form of a patch. We're gathering the necessary resources to assist in creating this fix. This is expected to take multiple hours to develop and test. In the meantime, there's a workaround available to customers. Details of the workaround can be found here: https://help.salesforce.com/s/issue?id=a02Ka00000mGFWI We have also determined that this issue could impact any Commerce Cloud customer using SOAP-based Web Services Description Language (WSDL) integrations, and not just third-party integrations, as was previously understood. We'll provide an update in 3 hours or sooner if additional information becomes available.

9. monitoring May 14, 2026, 03:41 PM UTC

   We are currently developing a fix-forward patch, which is expected to take several hours to build, validate, and deploy. In the meantime, this workaround remains available to customers. Details of the workaround can be found here: https://help.salesforce.com/s/issue?id=a02Ka00000mGFWI We'll provide an update in 4 hours or sooner if additional information becomes available.

10. monitoring May 14, 2026, 08:07 PM UTC

    The fix-forward patch is currently being confirmed in a testing environment. Once validation is confirmed, we'll proceed with full deployment to the entire fleet, which is expected to take several hours. In the meantime, this workaround remains available to customers. Details of the workaround can be found here: https://help.salesforce.com/s/issue?id=a02Ka00000mGFWI We'll provide an update ‌as additional information becomes available.

Read the full incident report →

Started May 13, 2026, 05:54 PM UTC· resolved May 13, 2026, 06:27 PM UTC

1. identified May 13, 2026, 05:54 PM UTC

   Disruption Started: tableauServiceDisruption

Read the full incident report →

Started May 12, 2026, 02:17 PM UTC· resolved May 12, 2026, 04:54 PM UTC

1. identified May 12, 2026, 02:17 PM UTC

   Degradation Started: featureServiceDisruption

2. monitoring May 12, 2026, 02:18 PM UTC

   We're aware of an issue impacting sandboxes. Customers attempting to deploy packages to sandbox environments are receiving errors and are unable to complete deployments. We've identified this as a regression introduced by a recent deployment and are working on rolling this back. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring May 12, 2026, 02:32 PM UTC

   Investigations have highlighted that the start time is earlier then previously understood and we've updated the posting. Additionally, we've confirmed that this issue only impacts deployments containing list views. We're in the final stages of preparing the roll back and we'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring May 12, 2026, 02:56 PM UTC

   We're continuing with the final stages of preparing to roll back the change that's causing deployments that contain a list view to fail to deploy. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started May 11, 2026, 12:05 PM UTC· resolved May 12, 2026, 07:55 AM UTC

1. identified May 11, 2026, 12:05 PM UTC

   Degradation Started: agentforcePerformanceDegradation

2. monitoring May 11, 2026, 12:05 PM UTC

   A subset of customers are experiencing an issue affecting Agentforce custom prompt templates. Customers may receive the following error message “Can't open prompt template. The URL contains a record ID for a prompt template that doesn't exist. Check the URL and try again”. We're in the process of engaging additional engineering teams to further investigate the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring May 11, 2026, 12:19 PM UTC

   We're currently investigating whether this issue is a result of a recent release. If confirmed to be related, we'll attempt to perform a rollback of the recent release to resolve the issue for affected customers. Attempts to use the "Draft with AI" functionality dependent on custom prompt templates are also failing. Standard prompt templates are not impacted. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring May 11, 2026, 12:57 PM UTC

   We are attempting to perform a roll-back on the release on a test instance. If this is successful, it will be applied to all impacted instances. In the event that the rollback is not successful, we'll attempt an emergency code fix. The development and testing of the fix is being done in parallel and is expected to take 60 minutes to complete. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

5. monitoring May 11, 2026, 01:11 PM UTC

   The roll-back of the recent release on a test instance was unsuccessful. We've identified the need to implement a configuration change to the impacted instances. The configuration change will act as a fix for the issue. Once this configuration change is developed, it'll be validated on a test instance and then rolled out to all impacted instances. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

6. monitoring May 11, 2026, 02:10 PM UTC

   Work is still underway to develop the configuration change needed to resolve the issue for affected customers. This is expected to take some more time to complete. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

7. monitoring May 11, 2026, 02:41 PM UTC

   We’ve completed the development of the configuration change and are currently verifying it on a test instance. If this proves successful, it'll be rolled out to all impacted instances. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

8. monitoring May 11, 2026, 04:45 PM UTC

   We’ve validated the fix, and it’s now progressing through our deployment build pipeline. We expect this process to take approximately three to four hours. Once complete, we'll perform a final round of validation before rolling out the fix to all affected customers. Upon further investigation, we have determined that the start time of the impact is earlier than initially understood. We have now 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 upon completion of the fix or if significant information becomes available.

9. monitoring May 11, 2026, 09:01 PM UTC

   The fix has been fully validated and is being prepared for deployment to all impacted instances. This process is expected to take several hours to complete. We'll provide another update once the fix has been deployed to all impacted instances, or sooner if additional information becomes available.

Read the full incident report →

Started May 08, 2026, 05:53 AM UTC· resolved May 08, 2026, 07:21 AM UTC

1. identified May 08, 2026, 05:53 AM UTC

   Degradation Started: muleSoftPerformanceDegradation

2. monitoring May 08, 2026, 05:59 AM UTC

   We're aware of a performance degradation impacting Anypoint MQ services. A subset of customers may experience errors when their applications attempt to interact with the message queue. We're actively working to restore full service. We'll provide an update in 60 minutes or sooner if additional information becomes available.

3. monitoring May 08, 2026, 06:31 AM UTC

   We have restored service for the related telemetry and ingestion functionality; however, some customers may still see connection loss errors when their applications interact with the message queue. We're investigating the remaining connectivity issues, and working with our third-party infrastructure providers to isolate the cause and restore full service. We'll provide another update in 60 minutes or sooner if additional information becomes available.

4. monitoring May 08, 2026, 06:53 AM UTC

   On further analysis, we've narrowed the issue down to a network routing and connectivity problem within the underlying infrastructure. We have teams focused on this component and continue to work closely with our third-party infrastructure providers to isolate the trigger and restore full service. We'll provide another update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →