Loading

Automated updates in Salesforce are not captured by Account Engagement

Publiseringsdato: Sep 30, 2025
Beskrivelse
This situation comes down to database transactions and the Apex Order of Execution.

An example scenario:
— Account Engagement gains some new information.
— Account Engagement syncs this information to Salesforce.
— As a result of the new information, automation in Salesforce changes the value of a field.
— This change is not reflected in Account Engagement after being set in Salesforce.

When a sync occurs, Account Engagement starts the transaction and our updates come in before pretty much anything else in the order starts. So we make our change, and assume we’re done. But the transaction is far from over. Even though the whole transaction may take less than a second to complete, a good deal happens after Account Engagement does its part.

Later in the process, workflows and triggers can be invoked to make further changes to any fields. Account Engagement doesn’t monitor what happens  after it makes its changes. It also doesn’t re-query Salesforce after the commit, because the LastModifiedDate timestamp will match the timestamp from when Account Engagement started the sync. Account Engagement is smart enough to know not to re-sync if the last time a record in Salesforce was update matches the last time we synced to said record. If we didn’t do this, we’d be stuck in an infinite sync loop.

End result: Account Engagement thinks it has the most recent data after the transaction closes, because it doesn’t realize that there was further modification done during the transaction. 
Løsning

The workaround here is to delay the Salesforce automations so that the transaction with Account Engagement fully completes before making another update. In this way, the new information from Salesforce can trigger another sync into Account Engagement . 

This can be done using Asynchronous Apex or Scheduled Paths in Flows or in Apex with the ‘@future’ method.

Knowledge-artikkelnummer

000381069

 
Laster
Salesforce Help | Article