Getting a Flow error when Heroku Connect syncs to Salesforce

Resolution

We often see this error from Salesforce when the triggered Flow has been designed in a way that prevents it from being able to keep up with the number of updates that Connect sends to Salesforce at a time. Unfortunately, the only way to resolve this error is to re-engineer the Flow in question so it is able to keep up with the number of record updates that we send to Salesforce.