Salesforce Triggered Sends with subsequent rule can prevent evaluation of other triggered sends
Trailblazer Community

Salesforce Triggered Sends with subsequent rule can prevent evaluation of other triggered sends

Marketing Cloud Integrations

Last updated 2019-11-25 ·Reference W-5482327 ·Reported By 2 users

In Review

Summary
Salesforce Triggered Sends with subsequent rule can prevent evaluation of subsequent triggered sends.

Repro
- Create 2 Salesforce Triggered Sends on the same Object
- Set both Triggered Sends to "new record is created or existing record is updated to subsequently meet criteria"
- Set each Triggered Send to look a different field on the Object
- Update each field separately
- The first Triggered Send is sent but the second one is not evaluated

Workaround
Replace the standard Triggered Send Apex Trigger to call each Triggered Send by name;


trigger SalesforceTriggeredSendObject on Object (after insert, after update) {
if (!Test.isRunningTest()) {
et4ae5.triggerUtility.automateByName('Object ', 'TriggeredSend1');
et4ae5.triggerUtility.automateByName('Object ', 'TriggeredSend2');
}
}

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.