Feature Disruption

The Salesforce Technology team has successfully validated the release and is actively rolling it out to the impacted instances, and the team is closely monitoring it to ensure its effectiveness.

We’ll provide an update as soon as the deployment is complete or if any additional information becomes available.

With testing now completed in multiple non-production environments the Salesforce Technology team has begun deploying the patch release to one production instance. The team will then test and monitor performance to understand whether this has been successful. Once validated, this will be rolled out to additional instances.

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

The Salesforce Technology team continues to develop the patch release to restore services for customers. The patch release is currently being tested in controlled environments, and the results have been promising. Once testing is complete the patch release will be rolled out to impacted instances. We do not yet have an estimated time for when this deployment will start. The team can confirm that a revised start time has been identified, as of 11:50 UTC, March 3, 2025.

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

As investigation continues, the Salesforce Technology team has further identified that the issue is impacting customers’ ability to create new models through the Bring Your Own (BYO) LLM feature, as well as the ability to use existing models already created. Work continues to develop a patch release to mitigate the issue.

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

The Salesforce Technology team continues to investigate the issue. Work is underway to develop a patch release to mitigate the issue.

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

We have identified an issue with the Bring Your Own LLM feature in Einstein Studio, which began at 11:50 UTC on March 3, 2025. Affected customers may encounter errors when using a configured LLM. Our teams have identified the trigger and are testing a solution that is expected to remediate the issue.

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