Feature Disruption

We have successfully propagated the fix to many affected instances. To ensure accuracy, we're separately validating and publishing the precise end time of feature disruption for those instances through individual Trust updates.

We're continuing the rollout in a staggered manner to minimize disruption to your business.
We'll keep you informed and provide an update as soon as the fix is deployed to your instance, or sooner if there's a significant development.

We identified the technical trigger, and are in the process of rolling out a code-level fix across all impacted instances. As services are restored we will move instances from this Trust post to ensure accuracy. Customers on the removed instances will receive a separate update with details specific to their environment, including out of impact time.

We will continue to roll out the fix across the remaining impacted instances, and will provide the next update once the fix has been implemented across all instances.

We've identified the required additional changes, have completed validations and are now implementing the fix in production. A Known Issue article remains available for impacted customers, with additional details and workaround information: http://sfdc.co/98Cf4.

We'll provide an update as soon as the fix is implemented, or upon any significant other developments.

The fix was deployed to a test instance, and upon validation, we have determined that the issue persists. We're working on additional configuration changes that'll be deployed and tested before rolling out the change across the impacted instances.

Thank you again for your patience. We’ll provide further updates on our progress as and when they become available.

We continue working on a code-level fix to restore saving changes to the impacted events.
In the meantime, a Known Issue article has been published with additional details and workaround information: http://sfdc.co/98Cf4

Thank you again for your patience. We’ll provide further updates on our progress as and when they become 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 have successfully disabled the feature that was triggering the issue, which has stopped the error from impacting new event updates on the impacted instances. Our monitoring confirms a reduction in error rates following this action. We are now focused on a code-level fix to resolve the issue for existing events that were modified during the disruption. This fix is scheduled for an emergency release. Once safely tested and validated, the deployment is expected to take several hours to reach all environments.

Thank you again for your patience. We’ll provide further updates on our progress as and when they become available.

Note: ARE6 was mistakenly included in the impacted instance list and will be removed. This will be the final communication for customers on ARE6.

We noted a feature disruption beginning at 12:00 UTC on March 23, 2026 impacting Salesforce event records. As a result, a subset of customers using Einstein Activity Capture (EAC) may experience error messages when attempting to update and save existing events. We have identified the cause and are currently working to disable a specific feature to prevent further impact.

We will provide an update in 30 minutes or sooner as more information becomes available.