Process builder is not triggered when Time dependent workflows are used

Apex , API , Workflow , Flow , Winter 16 , Process Builder

Process builder is not triggered when Time dependent workflows are used

In Review ·Reported By 221 ·Updated 6 days ago

Process flow consisting of a chatter action "Post to Chatter" throws an error when deployed via change sets

Change Sets , Flow

Some customers have observed their process flow that was created/updated via a deployed change set throws the following error when the conditions for the flow are met: “The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301XXXXXXXXXXX....

In Review ·Reported By 22 ·Updated 5 days ago

Screen Flows Launched by Quick Actions Display Duplicate Labels in Communities

Communities , Flow

Organizations that attempt to launch a Screen Flow in Communities via a Quick Action will find that the Label / Header associated with the action will display twice.

In Review ·Reported By 15 ·Updated 7 days ago

Custom Metadata Type not being sorted as expected

Apex , API , Custom Objects , Flow

Sorting order not being used in SOQL with Custom Metadata Type when sort field is not in column queried. This result in the order not being returned properly with Flows, API, Apex, and any functionality which would use a SOQL query for Custom Metadata Type. Consider a Custom metadata type called MD_NUMBER__mdt...

In Review ·Reported By 39 ·Updated 8 days ago

When receiving "Too Many SOQL queries: 101" error from process builder flow, the debug log does not show these SOQL

Apex , Workflow , Flow , Process Builder

As per the following document: https://help.salesforce.com/articleView?id=process_limits_scheduled.htm&type=0&language=en_US when salesforce looks up an existing record it uses a SOQL towards the SOQL limit. This allows the user to hit the "Too Many SOQL queries: 101" error, yet if debug logs...

Fixed - Summer '18 ·Reported By 138 ·Updated 9 days ago

Process Builder scheduled actions that are grouped for bulkification and failed due to limits are not retried

Workflow , Flow , Process Builder

Process Builder scheduled actions are executed in a batch of groups run within a single transaction. This can sometimes lead to limits being exceeded. As an example, "Too Many SOQL queries: 101". If a group within the batch fails due to Apex limits, the actions within the failed group should be...

Fixed - Summer '18 ·Reported By 44 ·Updated 9 days ago

Duplicate Lead Assignment Rule email notifications are sent when a Lead is inserted via API

API , Flow

Duplicate Lead assignment rule notification emails are sent for Leads created via API (e.g. Pardot, Apex).

Fixed - Summer '18 ·Reported By 40 ·Updated 9 days ago

Flow dynamic record choice sort order not preserved when installed in subscriber org

Packaging , Partner , Flow

When a managed package which includes sorted flow dynamic record choice element is installed in a subscriber org, the sort order is not preserved in the subscriber org.

Fixed - Summer '18 ·Reported By 14 ·Updated 9 days ago

Deployment Validation fails fails with “We can't find an action with the name and action type that you specified.” error

Flow , Process Builder

Consider a Process calling an invocable flow. Create a process (which call an invocable flow), a screen flow and an invocable flow such that the alphabetical order of their names results in the above order. Create a change set with these components and upload to prod. Validate the change set in prod...

Fixed - Summer '18 ·Reported By 8 ·Updated 9 days ago

Process Builder scheduled actions that are grouped for bulkification and Static Variables are not scoped as expected in Scheduled Actions

Workflow , Flow , Process Builder

Process Builder scheduled actions are executed in a batch of groups run within a single transaction. Static Variables are not scoped as expected in Process Builder Schedule Action

Fixed - Summer '18 ·Reported By 2 ·Updated 9 days ago

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