Known Issues · Performance
Users using LEX with Chrome version 54 may experience issues selecting text on their records. As the users are unable to select the text they will not be able to copy and paste, however edit a record will allow you to select and copy the details.
In Review ·Reported By 84 ·Updated 2021-06-02
When running a query against the EmailMessage object and a selective filter is used on CreatedDate sometimes this will run slowly or time out. This is due to a missing standard index on this field.
Fixed - Winter '16 ·Reported By 13 ·Updated 2021-05-26
Customer using Safari may experience errors when opening record pages in lightning.
Fixed - Spring '17 ·Reported By 11 ·Updated 2021-05-26
Name field with only special characters won't use index while executing the query. It is a expected behavior.
Fixed - Spring '16 ·Reported By 10 ·Updated 2021-05-26
When a user starts creating a record in Lightning Experience, and is experiencing an internet disruption at the time they click Save, we show a message "Check your Internet connection and try again", with a "Try Again" button. Clicking that "Try Again" button once connection is restored clears the...
Fixed - Summer '21 ·Reported By 6 ·Updated 2021-05-26
Strategy builder choice not defaulting if an Next Best Action component is present in Lightning App Builder
No Fix ·Reported By 1 ·Updated 2021-05-20
Search operations on pages like "Add Sharing", Report Folder Sharing, or Edit Public Groups and/or Queues that use UROG (UserRoleOrGroup) components are frequently timing out in Orgs with a large number of users.
In Review ·Reported By 3 ·Updated 2021-04-22
When opening a profile in an org with a large amount of custom metadata, users may experience delays and/or timeouts. This occurs due to dependency checks running against the large number of custom objects/fields/permissions/classes etc... when the profile is loaded. For example if there are 1000+ apex...
In Review ·Reported By 13 ·Updated 2021-04-08
If a lightning component is loaded the first time, the init method is called and executed as expected. But subsequent loads (with different URL) do not reinitialise the component at all and the init method does not fire. This is specific to console App.
No Fix ·Reported By 4 ·Updated 2021-01-15
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.