Journey Builder Salesforce Integration Events will not always fire if another Process Builder finishes later in the same transaction
Trailblazer Community

Journey Builder Salesforce Integration Events will not always fire if another Process Builder finishes later in the same transaction

Marketing Cloud Integrations , Marketing Cloud Journey Builder

Last updated 2020-08-21 ·Reference W-4262795 ·Reported By 80 users

Fixed

Summary
Customers may experience a condition in which their Salesforce Data Event will not fire if another process is updating the object that meets the condition to make the JB Process Builder trigger.

Repro
1) Create a Journey with a Salesforce Data Event pointed to the Case object.
2) Make the Contact the selection for "Who to Inject".
3) Create a process in Process Builder to update case object to assign a Contact to the case if non are assigned.
4) Create a case with no contact.

NOTE: The Journey Builder process may fire prior to the other process creating a contact resulting the in the Journey not having an object to inject.

Workaround
Update: On October 5th (2019) the Marketing Cloud Connect package was updated to set the Publish Behavior on the Platform Event to Publish After Commit for all Salesforce Entry Events. This change ensures that new Journeys are created in a way to publish data to Marketing Cloud after the data is saved within the Org.

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.