Salesforce Known Issues

Approval Merge Fields Have Wrong Value for Approval Related Emails


When using Approval Merge Fields, the values may be incorrect when used as approval related emails (final approval/rejection, immediate email alert). Note: the approval merge fields work correctly in the Approval Assignment Email.

In Review ·Reported By 314 ·Updated Yesterday

Emails not getting sent when Notify Assignee is enabled for Workflow Field Updates on Case object


If a Workflow Rule w/ a Field Update is setup to change ownership on Case records, the "Notify Assignee" option fails to send an email to the new owner when Cases are created through the API and/or Visualforce pages. This also applies to Cases created by Email-to-Case, as this functionality is dependent...

In Review ·Reported By 100 ·Updated 3 days ago

Feed Post not visible after User creates a record using a Quick Action if Process updates a field on the record

Workflow , Process Builder

Feed Post not visible after User creates a record using a Quick Action if a Process/Workflow updates a field on the record.

In Review ·Reported By 59 ·Updated 2 days ago

Geolocation fields in WorkflowOutboundMessage cause Internal Server Errors in deployments

Workflow , Metadata , Change Sets

Sometimes in a deployment while trying to upsert a WorkflowOutboundMessage, if the outboundMessage metadata includes a 'Geolocation' field a null pointer exception Internal Server Error (ISE) is thrown in the deployment.

In Review ·Reported By 4 ·Updated Yesterday

Workflow Rule Criteria Set to "Subsequently Meets" But Fires When Lookup Is Edited

Platform , Workflow , Summer 18

Suppose you have a workflow rule with criteria set to Created and Edited to Subsequently Meet Criteria. In this situation, a record initially meets the workflow rule and fires (as expected). If you do not change the value of the field used in the workflow criteria, you are not editing the record to 'subsequently'...

In Review ·Reported By 10 ·Updated 3 days ago

Change Owner notification is being triggered via workflow or update in an action in Lightning when “Notify Case Owner of New Case Comments” is checked

Service , Workflow , Lightning

Cases created in lightning experience will generate an email notification to the new case owner when the ownership is changed via a workflow rule and the “Notify Case Owner of New Case Comments” is select in Support Settings. This is regardless if the option to notify assignee is selected in the workflow...

In Review ·Reported By 2 ·Updated 3 days ago

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


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 162 ·Updated 9 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 118 ·Updated 9 days ago

Email Alerts to Account Team are not sent from Workflow on Activities

Workflow , Process Builder

An Email Alert on Task or Event with "Account Team" recipients does not send an email to those Account Team Members, even when triggered by a Task/Event that is related to an Account.

In Review ·Reported By 62 ·Updated 10 days ago

Error CANNOT_EXECUTE_FLOW_TRIGGER when the flow contains Custom metadata type lookup relationship

Apex , Workflow , Flow

Invocation of a flow fails with an unknown error (With Salesforce Error Id and Stacktrace Id) if the flow contains lookup to custom fields in the custom metadata type

In Review ·Reported By 1 ·Updated 11 days ago

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