Salesforce Known Issues

Known Issues · Process Builder

ProcessBuilder input which is a formula containing BR() results in BR_ENCODED_ text when used in a Flow

Flow , Process Builder , Summer 19

ProcessBuilder input which is a formula containing BR() results in BR_ENCODED_ text when used in a Flow

In Review ·Reported By 9 ·Updated 24 days ago

Process builder not updating a field when a roll up summary is changed to trigger the process

Process Builder

Process builder in Order object will not set a field equal to a rollup summary field when adding new product on the order record. This can also affect removing products.

In Review ·Reported By 6 ·Updated 28 days ago

Signing up an org with trialforce template changes formula from custom field name to fieldID from the origin org

Process Builder

When a Process Builder in a TSO org includes formulas referring to custom fields, those references become replaced with the Ids of the custom fields when a trialforce template is created. This causes the process to be invalid in orgs created using that trialforce template.

In Review ·Reported By 28 ·Updated 2019-12-23

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 99 ·Updated 2019-12-18

Flow with lightning component does not carry the changed values into next screen when toggling between Previous and Next screens

Sandbox , Flow , Process Builder , Lightning , Winter 20

After entering values in the flow screen and clicking NEXT and then going back to the previous screen by clicking on the Previous button, changing the value and clicking Next, the changed values are not carried over.

Fixed - Winter '20 Patch 15.0 ·Reported By 5 ·Updated 2019-12-15

When using a custom "Log a Call" Quick Action on Cases, the "[Person] logged a call" Feed Item is not included in the Chatter Feed when updated

Summer 16 , Process Builder

When using a custom "Log a Call" Quick Action on Cases, the "[Person] logged a call" Feed Item is not generated if a Process Builder flow updates the generated task. When saving, you will notice that you receive a message that lets you know it was successful, the Chatter Feed refreshes and the Feed...

In Review ·Reported By 28 ·Updated 2019-12-12

Flow (INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY) error - error goes away with a "Screen element" in between

Performance , Platform , Sharing , Flow , Process Builder

Flow (INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY) error - error goes away with a "Screen element" in between

In Review ·Reported By 7 ·Updated 2019-12-10

Delays seen in processing messages of some Time Based Workflows & Scheduled Actions in Process Builder

Performance , Workflow , Messaging , Flow , Process Builder

Salesforce is seeing some delays of over 40 minutes in the processing of time based workflows and scheduled actions in Process Builder which may cause stacking of workflows and delay in creation of records depending on the setup of the action.

Fixed - Winter '20 Patch 11.5 ·Reported By 5 ·Updated 2019-12-06

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 41 ·Updated 2019-12-03

Process Builder updates Task - WhoId field only through inline edit but not through normal edit

Process Builder

In some cases the WhoID field not updated through Process builder when Task is edited using normal edit but works just find when using inline edit.

In Review ·Reported By 25 ·Updated 2019-11-28

Prev | 21 to 30 of 156 | 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.