Salesforce Known Issues
Trailblazer Community

Known Issues · Developer Console

Code coverage issue

Apex , Developer Console

Summary: ApexCodeCoverage records may be missing for Apex classes when Apex test classes run for more than 3 minutes. For example, assume we have the class ApexClassA, which is tested by: * ApexClassA_Test1 (has 2 methods) and * ApexClassA_Test2 (has 10 methods) If you run just ApexClassA_Test1...

In Review ·Reported By 3 ·Updated Yesterday

New!Deployment failing with test class failure on Spring'23 org with Internal Salesforce Error

Apex , AppExchange , Developer Console , Change Sets , Spring 23

When running the test classes during deployment we receive a Gack error "(2141843226)" after Spring 23 release.

Scheduled - Spring '23 Patch 7.0 ·Reported By 0 ·Updated Today

Scrutiny to update Invalid dates in VisualforceAccessMetrics records.

Apex , VisualForce , Data Export , Developer Console

VisualforceAccessMetrics query is failing due to corrupted data in LogDate Field

In Review ·Reported By 8 ·Updated 16 days ago

Upsert creating duplicate records while making the External Id field unique

API , Data Loader , Developer Console , Data Import Wizard

Duplicate records are getting created while performing an upsert and making the external Id field unique.

In Review ·Reported By 3 ·Updated 2022-12-05

Bulk Upsert and Update of CaseComments don't work correctly

Apex , Performance , Platform , Developer Console

Upserting and Updating the CaseComment object methods gives error: QUERY_TIMEOUT, Your query request was running for too long. This happens for Lists of CaseComments upserting or updating in bulk. This occurs in test methods and outside test methods System.DmlException: Update failed. First...

In Review ·Reported By 27 ·Updated 2022-12-02

SOQL query of custom metadata types inside for Statement causing query performance issue than outside for statement

Apex , Developer Console

As per the Salesforce best practices document (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/langCon_apex_loops_for_SOQL.htm), for large data sets, SOQL can be written inside FOR statement. However, that affects the CPU time consumption of that transaction -- which is expected...

In Review ·Reported By 1 ·Updated 2022-11-10

SOQL on PermissionSetAssignment is returning different results when "ORDER BY PermissionSet.Name" is used vs omitted.

Apex , Developer Console , Financial Services Cloud

SOQL on PermissionSetAssignment is returning different results when "ORDER BY" is used on PermissionSet relationship fields. If "ORDER BY" clause is not used on the relationship fields, all the records show up (based on filter criteria, if applied).

In Review ·Reported By 1 ·Updated 2022-10-24

When using apex:milestoneTracker component in Visualforce, it shows discrepancy in standard and custom lightning app

VisualForce , Sandbox , Developer Console , Service Cloud Console , Lightning

When using apex:milestoneTracker component in Visualforce page, there is a discrepancy in the standard and custom lightning app. When user adds the milestoneTracker in the lightning app and click on the 'Milestone_Name' link and either click save or cancel button, than user is redirected to the last...

In Review ·Reported By 1 ·Updated 2022-10-20

Unbalanced CODE_UNIT_STARTED and CODE_UNIT_FINISHED in Debug logs

Apex , Developer Console

Create org with a managed before trigger and an unmanaged before trigger. Make sure managed trigger executes first (e.g. on Lead) Enable debug logs and do DML to fire the trigger. On the captured Debug logs observe CODE_UNIT_FINISHED for the unmanaged trigger is never emitted which results in unbalanced...

Fixed - Spring '23 ·Reported By 1 ·Updated 2022-08-15

Email when sent using method "UserManagement.sendAsyncEmailConfirmation" is displaying FROM NAME as email address only

Apex , Developer Console , Communities

Email when sent using method "UserManagement.sendAsyncEmailConfirmation" is displaying FROM NAME as email address only From Name: com1-w11548497 Email Address: w11548497@salesforce.com If you set the above in a community, using sendAsyncEmailConfirmation() will set the From header to "w11548497@salesforce.com"...

In Review ·Reported By 1 ·Updated 2022-08-12

1 to 10 of 38 | 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.