Getting a Flow error when Heroku Connect syncs to Salesforce


The following error (or a part of it) is encountered in the Heroku Connect dashboard logs, or in the sf_message field of the _trigger_log or _trigger_log_archive table, after Heroku Connect has attempted to send records updates to Salesforce which triggers a Flow.

The record couldnt be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID {{SALEFORCE_ID}}. Flow error messages: This interview has been terminated as another interview in the same bulk execution request failed with the following error: An unhandled fault has occurred in this flow

An unhandled fault has occurred while processing the flow. Please contact your system administrator for more information. Contact your administrator for help.


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. 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.

Ask on Stack Overflow

Engage with a community of passionate experts to get the answers you need

Ask on Stack Overflow

Heroku Support

Create a support ticket and our support experts will get back to you

Contact Heroku Support