Feature Disruption

The fix was released, and the team has validated that it was successful. Customers on the following instances: DEU72, DEU128, EU50, NA167,USA632, and USA926 are no longer impacted. Customers on these instances will receive a separate notification outlining the start and end impact times for their instance.

The remaining instance, NA238, will receive the release tomorrow as it is a special use case and requires additional monitoring. Further updates regarding instance NA238 will be provided as additional information becomes available or upon release completion.

We identified a fix for the issue and are working on releasing it to the impacted instances. This process will be monitored closely and is expected to take several hours.

We’ll provide another update as additional information becomes available or upon completion of the release.

We have identified the trigger for the issue and are continuing to develop and validate a fix to resolve it. This process is expected to take multiple hours to complete.

We’ll provide another update as additional information becomes available.

The team has confirmed an increased impact radius. The instances DEU72 and DEU128 will be added to the impacted instance list. The instance USA592 is confirmed as not affected by the issue and will be removed from future communication.

We’ll provide an update in 60 minutes or sooner if additional information becomes available.

The engineers have identified a fix, which is currently being validated and will be further tested before deployment.

We’ll provide an update in 60 minutes or sooner if additional information becomes available.

Further investigation determined that this issue is not due to the recent release. The issue is believed to be due to a bug. Teams are working on a fix forward. This will be initially tested in a staging environment and validated.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

As part of the Winter release, Java mail has been migrated to Jakarta mail. Post-migration, the application attempts to look for the old references and gets a messaging exception error, which is no longer available in Core and Hyperforce instances. This is what triggers the impact for customers. Teams are actively discussing how to redirect the connection references. Additional teams have been engaged to assist with the investigation.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

At 12:27 UTC on October 08, 2024, Salesforce engineers became aware of a feature disruption. Emails sent to the Email-to-Case (E2C) address are not generating cases after the Winter release. The Technology team is identifying the impact radius and exploring multiple paths to fix the issue.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.