Salesforce Known Issues
Trailblazer Community

Data updates are not reflected in UI after a Visualforce+Apex update in Lightning Experience

Apex , VisualForce , Lightning

When data is updated from an Apex controller and redirected to the detail page in Lightning Experience, the updated data is not seen in the UI, even though the data is updated in the database. This is an intermittent behavior and could happen when we are performing the updates continuously and redirecting...

In Review ·Reported By 1338 ·Updated 5 days ago

invalid query locator error occurs when iterating child objects in parent-child relationship query result

Apex

Invalid query locator error occurs when iterating child objects in parent-child relationship query result if CLOB fileds are included in the query and there are 200 child records.

Scheduled - Summer '21 ·Reported By 236 ·Updated 2 days ago

Testing HTTP Callouts from Async Apex throws "System.CalloutException"

Apex , Platform

Testing HTTP Callouts from Async Apex fails after inserting a CollaborationGroup or SetUp objects like User , ContentVersion, and it throws "System.CalloutException" Exception: System.CalloutException: You have uncommitted work pending. Please commit or rollback before calling out. The error also depends...

Scheduled - Spring '21 ·Reported By 123 ·Updated Yesterday

Custom error messages not displayed in Lightning Experience when uploading files

Apex , Content and Files , Summer 17

Server error messages (added via addError() for instance) are not displayed in various scenarios (e.g. file upload) in Lightning Experience. They are displayed as expected in Classic.

In Review ·Reported By 117 ·Updated 2 days ago

User object trigger does not get fired when the User object is modified via "Assign Users to Role"

Apex

Let us say we have an after update trigger on the User object. The trigger should fire when there's a role change. The role on the User can be changed in two ways: 1) Edit user and update the role 2) "Assign Users on Role" - A button on Role The User object trigger fires on #1 scenario but NOT...

In Review ·Reported By 33 ·Updated Yesterday

ObfuscateUser() method invoked in trigger context throws an exception when trying to update user record.

Apex

System.UserManagement.obfuscateUser() invoked in trigger context leads to exception when updating user record

In Review ·Reported By 16 ·Updated Yesterday

SingleEmailMessage.setEntityAttachments() method does not keep attached files on EmailMessage records in Cases

Apex

The SingleEmailMessage.setEntityAttachments() method attaches files to EmailMessage records when the SingleEmailMessage.setWhatId() points to an Opportunity. When you use the UI to manually send an email with an attachment from a Case record the file gets attached to the EmailMessage related list...

In Review ·Reported By 21 ·Updated 2 days ago

Multiple email notifications are sent when changing the record owner in Lightning

Apex

In lightning, multiple email notifications are sent when the owner field is changed in UI along with "Send notification email" check box enabled. This happens when there is apex trigger to update the related records owner field. The same records when changed in classic do not sent multiple email.

In Review ·Reported By 135 ·Updated 5 days ago

Script thrown exception in Apex callouts

Apex

When a server responds to an apex callout with empty response body along with Content-Encoding header set to gzip, apex throws System.CalloutException: Script-thrown exception

In Review ·Reported By 13 ·Updated 2 days ago

New!Process builder subscribed for platform event may fail with Error ID 1915218205-159540 (-1214425933)

Apex , Metadata , Flow

Process builder listening for a platform event fails with "A platform event message couldn’t launch the flow. Contact Salesforce Customer Support with Error ID 1915218205-159540 (-1214425933)", when an apex is invoked which is making a callout along with schema.getGlobalDescribe() call.

In Review ·Reported By 1 ·Updated Yesterday

1 to 10 of 864 | Next

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.