Delay in SFDC Sync Causes Email to be Sent With Unpopulated Tokens
Description description
- Delay in SFDC Sync causes email to be sent with unpopulated tokens
- Wait steps in campaign designed to prevent race conditions are sometimes not long enough for the SFDC Sync to complete
- Wait steps cause a delay in receiving the email after filling out a form, for example
Resolution resolution
- Split the Smart Campaign into two separate campaigns
- The first campaign runs the sync activities, but does not send the email
- The second campaign triggers off of the Data Value Changes resulting from the sync and sends the email with the email tokens populated, ensuring there is adequate time for the email to be populated with the proper tokens from the record’s activity log
recommendation-more-help
experience-cloud-kcs-help-kbarticles