The fleet-wide deployment of the fix is progressing as expected. Customers whose instances have received the fix will soon receive a separate, dedicated notification, including a summary of the incide

Update timeline

1. identified Jul 07, 2026, 11:39 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Jul 07, 2026, 11:39 AM UTC

   We're investigating an issue affecting the Dynamic Highlights Panel when customers are accessing it using the latest update to Chrome or Edge browsers. The panel isn't rendering the primary field values correctly for affected customers . This is impacting their ability to view key record information such as case numbers. We've engaged relevant teams to assist in the investigation. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

3. monitoring Jul 07, 2026, 11:52 AM UTC

   We’re‌ testing a work around which we believe will bring affected customers out of impact. If successful, we'll share the details of the work around with customers here. In parallel, we're also investigating a long term fix to resolve this issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. identified Jul 07, 2026, 12:02 PM UTC

   Degradation Started: performanceDegradation

5. monitoring Jul 07, 2026, 12:02 PM UTC

   Work is still underway to identify a viable workaround for customers. We’ve established that the level of impact differs from what was initially understood and is considered a performance degradation rather than a feature degradation as was previously communicated. We've also determined that the start time of the impact is different than initially understood. We've updated the incident posting to reflect the current impact and start time accurately. We apologize for any confusion this may have caused. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Jul 07, 2026, 12:25 PM UTC

   We're testing a configuration change that we believe will bring customers out of impact. Once validated that it's successful, the change will be rolled out to all affected instances. The testing is expected to take approximately 60 minutes to complete. In parallel, we're still testing a workaround for customers. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

7. monitoring Jul 07, 2026, 01:16 PM UTC

   We have determined that the proposed workaround which we were testing is not a viable option for customers. Our current focus is now solely on testing the configuration change, which is taking longer than expected. Additional teams have been engaged to assist with the testing. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

8. monitoring Jul 07, 2026, 02:12 PM UTC

   Upon further investigation we've been able to reproduce the issue and have identified workarounds which customers use. The details of the workarounds can be found here: https://help.salesforce.com/s/issue?id=a02g7000005pKxt We have determined that this issue is more complex than initially understood. We're working to engage browser vendors as part of this investigation. Internal testing on a configuration change are still underway. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

9. monitoring Jul 07, 2026, 03:13 PM UTC

   A possible path to resolve the issue is a configuration change. We're working to validate whether this is viable. We've engaged our release team and have them on standby to ensure that the configuration can be deployed if validated as a fix. In parallel, we have also engaged the browser vendor to assist with this investigation. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

10. monitoring Jul 07, 2026, 04:28 PM UTC

    We're continuing to work with our vendor and are validating a configuration change as a possible solution. Once validated, we'll deploy this change and monitor to ensure it fully resolves the issue. We’ll provide an update in 60 minutes or sooner if substantial changes come from our validations.

11. monitoring Jul 07, 2026, 05:43 PM UTC

    We are aiming to begin deploying the validated configuration change at approximately 19:00 UTC while continuing to work with our vendor to expedite their fix across all impacted browser versions. Please see this Known Issue article (https://help.salesforce.com/s/issue?id=a02g7000005pKxt) documenting available workarounds. We’ll provide an update as soon as substantial information is available.

12. monitoring Jul 07, 2026, 11:32 PM UTC

    We have identified a Cascading Style Sheets (CSS) rendering change introduced in a recent browser update as the cause of this issue. We’ve completed development and validation of a fix, and deployment is now underway fleet-wide. We have no clear indication of how long our fleet-wide deployment may take. We will provide the next update when we can clarify this. A period of monitoring will be undertaken once deployments are completed across all instances. Workarounds are documented and available via the Known Issue article: https://help.salesforce.com/s/issue?id=a02g7000005pKxt We’ll provide an update as soon as any new information becomes available.

13. monitoring Jul 08, 2026, 06:09 AM UTC

    We've made significant progress with the fleet-wide deployment of the fix. During the rollout, we identified and resolved a temporary issue that affected a small number of instances. The fix has now been deployed to the majority of instances, and the remaining instances are planned to be completed by 15:00 UTC, July 8. We will provide another update once the fleet-wide deployment is complete or if additional information becomes available.

14. monitoring Jul 08, 2026, 12:19 PM UTC

    The fleet-wide deployment of the fix is progressing as expected. Customers whose instances have received the fix will soon receive a separate, dedicated notification, including a summary of the incident and accurate start and end times.