Salesforce Known Issues
Trailblazer Community

Email Alert sending to all members of Queue and Queue email when "Send Email to Members" is not checked

Workflow

When an approval process updates the Record Owner to a Queue and sends out an Email Alert to the Record Owner, it is sending to each individual member of the queue and the queue email itself. This should not send out an email to them because the "Notify Assignee" and "Send Email to members" of queue...

In Review ·Reported By 285 ·Updated Today

In some Professional Edition orgs it is possible to create Field Updates, but there is no option to delete Field Updates once created.

Workflow

In some Professional Edition (PE) orgs it is possible to create Field Updates, but there is no option to delete Field Updates once created. Specifically, this behavior exists in PE orgs which have Entitlements, but which do not have Workflow.

In Review ·Reported By 52 ·Updated Yesterday

Lightning & Communities: User receives "insufficient access rights on cross-reference id" due to “Notify Case Owner of New Case Comment" being checked

Service , Workflow , Communities , Lightning

A user will receive the following error message when updating or creating a case in Lightning that triggers an email alert: "insufficient access rights on cross-reference id" This occurs when the email folder that the email template is contained in is not public or shared with the user and the...

In Review ·Reported By 49 ·Updated Today

Field Updates by Flow or Process are not triggering Case Escalation Rules

Service , Workflow , Flow , Process Builder

Case escalation rules are not being properly reevaluated after process/flow invoked field updates. Per Order of Execution doc (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm) escalation rules are to evaluate after Workflow and Process...

In Review ·Reported By 63 ·Updated 6 days ago

Unable to Deploy Field Update on Person Account Record Type

Workflow , Change Sets

When deploying a field update on Person Account Record Types through Change Set and it is failing with error "In field: lookupValue - no RecordType named Account.Record_Type_Name found"

In Review ·Reported By 53 ·Updated 6 days ago

Misleading Error Message for Process Failure When Accessing Non-Merge Accessible Field in ISCHANGED Function for Process Builder Criteria

Workflow , Flow , Process Builder

A process accessing the User field DefaultCurrencyIsoCode in a formula criteria is failing after Winter 21 or when the Critical Update “Check for Null Record Variables or Null Values of Lookup Relationship Fields in Process and Flow Formulas” is enabled.

In Review ·Reported By 7 ·Updated 6 days ago

In Summer '19, Automation Home (Beta) displays empty charts even when flows are in use.

Platform , Workflow

In Summer '19, Automation Home (Beta) displays empty charts even when flows are in use.

In Review ·Reported By 13 ·Updated 7 days ago

Submitting an entity for approval multiple times creates duplicate "Record Locked" entries in field history related list

Workflow , Spring 16

When a record which is already locked by an approval process is submitted for approval again, another "Record locked" entry is captured in the object's Field History.

In Review ·Reported By 4 ·Updated 7 days ago

Approval Process Step 2 does not allow you to choose a Partner or CP User as next Approver

Workflow

Users have a simple Approval Process with 2 steps. Both of the Steps allow you to choose the next Approver manually. On the first Step, you're allowed to select a User, Partner User, or Customer Portal User. That works fine. However, on the second Step, it only lets you select a User and not a Portal...

In Review ·Reported By 7 ·Updated 8 days ago

"Else Approve Record" Option is Unexpectedly Rejecting Records

Platform , Workflow

The “else Approve Record” option for Approval Processes only works if it’s specified on Step 1 of an Approval Process. When this option is specified in a subsequent Step, it automatically Rejects records instead of Approving them.

In Review ·Reported By 310 ·Updated 10 days ago

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