Salesforce Known Issues
Trailblazer Community

Hyperlink Formula Displaying _HL_ENCODED_ When Referencing Another Formula Field

Platform , User Interface

When a formula field displays a hyperlink, and in the formula it is referencing another formula field, the formula will display _HL_ENCODED_ instead of just the hyperlink text. For example, if the formula is: IF(formula_field__c > 0, HYPERLINK("", "Salesforce), null) It will...

In Review ·Reported By 137 ·Updated 3 days ago

Translation workbench export failed

Platform , User Interface

Translation workbench export failing

In Review ·Reported By 64 ·Updated 2 days ago

Delay in Processing Platform Events in Sandbox for Apex Triggers and Flows

Platform , Sandbox

In sandbox instances, there is a sporadic delay in processing platform events in Apex triggers, flows, and processes. Sometimes Apex trigger, flow, and process subscriptions fail in sandbox instances. The subscriptions stop and then are resumed later by the system from the latest stored unprocessed event...

In Review ·Reported By 69 ·Updated 3 days ago

Fuzzy Account Name Matching Rule not behaving as expected

Platform , User Interface

Duplicate Rules are not catching duplicates with fuzzy logic as expected.

In Review ·Reported By 42 ·Updated Yesterday

Error "Picklist value is not supported" when attempting to save Path Settings with "Guidance for Success" on Managed object


When attempting to create Path Settings on an object that is part of a Managed Package, the following error will appear when including "Guidance for Success" in the Path Settings: "Cannot insert Path Assistant Step Item: Picklist value is not supported" Attempting to create a similar path on...

In Review ·Reported By 166 ·Updated 5 days ago

State & Country Picklists Do Not Get Populated When Specified as a Quick Action Predefined Value

Platform , Service Cloud Console

With State and Country Picklists Enabled, if a quick action is created with a predefined value specified for a state/country field, and that field is on the quick action layout, then the picklists do not get populated correctly when using the quick action. Any additional pedefined field values specified...

In Review ·Reported By 93 ·Updated 4 days ago

Approval Merge fields (ie {!Approval_Requesting_User.Name}) values are incorrect in approval email

Activities , Platform , Email Clients , Flow , Process Builder

Approval merge field values are showing incorrect information in approval emails. When record is initially submitted for approval, in the email we are getting submitter name for both: {!ApprovalRequest.Process_Approver} (wrong value)* {!Approval_Requesting_User.Name} (right value) And when...

In Review ·Reported By 27 ·Updated 2 days ago

Unhelpful error message for Path setup Save error

Platform , User Interface , Lightning

When there is an error during Path Save, the browser always shows a generic error message "An unknown error occurred. Please try again. If the issue persists, contact Salesforce customer support." regardless of what the error is. There are at least a few different errors that can occur during Save, so...

In Review ·Reported By 36 ·Updated 3 days ago

Draft Email second save fails if Validated From Address field changes

Activities , Platform , Service Cloud Console , Lightning

Draft Email second save fails if Validated From Address field changes

In Review ·Reported By 10 ·Updated 2 days ago

New!Deployment failures in relation to "forceCommunity:availableForAllPageTypes"

Packaging , Platform

When deploying ExperienceBundle metadata to an org, some customers have experienced an issue where the deployment will fail with multiple "Implement forceCommunity:availableForAllPageTypes error for the Aura component" for standard components. However, when deploying the same metadata some time later...

In Review ·Reported By 2 ·Updated Yesterday

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