Salesforce Known Issues
Trailblazer Community

Known Issues · Process Builder

Duplicate Task assignment notification is sent to record owner when ownership is updated through Process builder/Flow in Lightning.

Process Builder

Duplicate Task assignment notification is sent to record owner when ownership is updated through Process builder in Lightning.

In Review ·Reported By 164 ·Updated 24 days ago

Process' Post to Chatter Action that posts a hyperlink ends up displaying "_HL_ENCODED_" in the record's feed instead of the proper URL/link

Chatter , Process Builder

In a Process, "Post to Chatter" actions posting a reference to a Formula (Text) Field with a Hyperlink() function ends up with a post displaying "_HL_ENCODED_" instead of the actual URL.

No Fix ·Reported By 102 ·Updated 24 days ago

Task notification email is not sent when the Task is created using a scheduled action in Process Builder

Process Builder

The notification email that Users are supposed to receive when a Task is assigned to them is not sent if the Task is created using a Scheduled Action in Process Builder.

Scheduled - Winter '23 ·Reported By 2 ·Updated 28 days ago

Process Builder changes the way the tasks are displayed in the case feed.

Activities , Process Builder

When you log a call in cases using a quick action with the action type "Log a Call" and the call is updated by a process, the call is displayed as a task and not as a call in the case feed.

In Review ·Reported By 40 ·Updated 29 days ago

Multi Customer Issue: Process Builder/Workflow Rule not firing causing issue with the data

Process Builder

Salesforce Technology team noted a feature degradation of the Salesforce Core Cloud Production environment. Impact: Customers may experience intermittent issues with Process Builder/Workflow Rule not firing even when the criteria is met.

Fixed - Spring '22 Patch 17.2 ·Reported By 266 ·Updated 30 days ago

Flow's sObject field values stored in a flow record variable are not accessible in the same flow variable after execution of the subflow element.

Flow , Process Builder

Flow's sObject field values stored in a record variable are not accessible in the same record variable after execution of the subflow element.

In Review ·Reported By 5 ·Updated 2022-04-21

Flow and Process Uses Incorrect Value of Field of Percent Data Type Spanning Two Objects

Process Builder

Evaluating a field of percent data type spanning two related objects returns the incorrect (not properly adjusted by dividing by 100) value in Process Builder and Record-Triggered After-Save Flow. Actual Result Percent value is not divided by 100. Expected Result Percent value is divided by ...

In Review ·Reported By 2 ·Updated 2022-04-07

When we select to deploy processes and flows as active and set the test coverage to 0%, test classes not related to the flow/process are running.

Metadata , Change Sets , Flow , Process Builder

In the process automation setting, When you set "Deploy processes and flows as active" to enabled and Specify a minimum test coverage percentage for flows to 0% and try to deploy my process and/or flow, we observe that the apex test classes not related to the process or flow are running.

In Review ·Reported By 13 ·Updated 2022-03-31

Processes that try to update certain user fields upon user edit, throws an Internal Server Error

Process Builder

Using a process to update either or both of the following fields during user creation or modification can cause an Internal server error (ISE): UserPreferencesReceiveNoNotificationsAsApprover UserPreferencesReceiveNotificationsAsDelegatedApprover Example ISEs: Salesforce Error ID: 1269375445-48832...

In Review ·Reported By 7 ·Updated 2022-03-30

Process Builder fails when fields containing merge syntax (such as {!Event.Phone}) are used in criteria.

Flow , Process Builder

Fields containing a value in merge syntax (such as {!Event.Phone}), will cause the Process Builder to fail with the following error if used in the process's criteria: -------- An error occurred at element myDecision (FlowDecision). The flow failed to access the value for myVariable_current.Phone because...

In Review ·Reported By 26 ·Updated 2022-03-25

Prev | 11 to 20 of 209 | 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.