Known Issues · 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 200 ·Updated Yesterday
After-Save Record-Trigger Flows don't execute when an Approval Process updates a record field using a field update with "Re-evaluate Workflow Rules after Field Change" option enabled. - Actual Result After-Save Record-Trigger Flow doesn't execute. - Expected Result After-Save Record-Trigger...
In Review ·Reported By 129 ·Updated Today
At present, it is possible to write Apex triggers on SurveyResponse, but due to lack of DML support of this entity, it is not possible to test this type of trigger, which prevents deploying them into production as Apex triggers must meet minimum 1% code coverage requirement.
In Review ·Reported By 64 ·Updated 2 days ago
Database.executeBatch() returns 000000000000000 when failing to acquire a flex queue lock. Database.executeBatch() require to obtain a flex queue lock. When they failed to acquire the lock even several times trying internally, the method returns 15 digit 000000000000000 ID as string value. In such...
Fixed - Summer '21 ·Reported By 54 ·Updated Yesterday
When attempting to add an Apex action to a Process Builder, users may receive an error like: Unfortunately, there was a problem. Please try again. If the problem continues, get in touch with your administrator with the error ID shown here and any other related details. Error ID: 1644647629-5767 (...
In Review ·Reported By 27 ·Updated Yesterday
CronTrigger rows for scheduled apex jobs are no longer copied over in Summer '17. However, CronJobDetails rows are still copied. Whenever customers run a sandbox copy for an org where scheduled apex jobs have been configured, the resulted sandbox org will have orphaned CronJobDetails rows.
In Review ·Reported By 23 ·Updated Today
RecordUpdated is not fired after second update. Fields that are requested from the server, but do not exist, are getting tracked is missing fields, which is causing refresh operations to not emit to ADS. Field can be requested by customers code or from some internal components.
No Fix ·Reported By 2 ·Updated Today
When we try to send an email from the case record that eventually is creating an EmailMessage Record. However, After updating the EmailMessage record Sometimes causing the below issue Error: STRING_TOO_LONG, HTML Body: data value too large
In Review ·Reported By 2 ·Updated Yesterday
Customer has scheduled batch job which involves the use of the getContentAsPDF() or getContent() methods. They noticed that the system failed to execute the scheduled jobs sometimes, usually around every 20 minutes, with the following error: Error: Scheduler: failed to execute the scheduled job Reason: ======= The...
In Review ·Reported By 1 ·Updated Yesterday
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 41 ·Updated 4 days ago
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.