Heroku Connect Log Messages and Common Errors

Last updated 07 September 2017

Heroku Connect keeps logs of its sync activity, which you can access from your Connect Dashboard by clicking the Logs tab. This article documents some of the errors and messages you may see in those logs.

Log errors

Summary for Opportunity status=DATA_SYNCED db=31 sf=31 pending=0 errors=0

If you’ve enabled application logging for your connection, you’ll see a variety of log lines related to Connect activity, including this one. This status line is logged periodically for each mapping. It contains these fields:

  • status: DATA_SYNCED means the mapping is fully synchronized. You may occasionally see other statuses relating to polling or bulk updates. If you see a status of SYSTEM_ERROR, you should visit your Connect Dashboard to investigate the error and resume your connection.
  • db: The current number of rows in the database table.
  • sf: The current number of rows in Salesforce. Please note that this count can occasionally be delayed.
  • pending: The count of records in the trigger log that are waiting to be written to Salesforce.
  • errors: The number of records in the trigger log that failed to write to Salesforce. If this number is not 0, you should query the trigger log for records where state = 'FAILED' and possibly attempt to retry writing them to Salesforce.

Attempted to open more than 10 queries to SFDC

Salesforce enforces a limit of 10 open queries per connected user. Heroku Connect synchronizes each mapping independently, and it will often sync several at the same time. Connect keeps track of how many queries it’s running across all of your mappings, and it won’t try to run more than 10 in parallel for each connection.

However, if you’re using the same user credentials elsewhere (or with another Heroku Connect connection), you might end up attempting to use more than 10 queries at a time. If you’re having this problem and you have multiple connections, try authenticating each connection with a different user account.

SYSTEM_ERROR (Unexpected error)

If your connection is reporting a SYSTEM_ERROR state, you can resume the connection from the Connect Dashboard to resume synchronization. Click the “Settings” link, then click “Manage Connection”. From there, you can click the “Resume” button to resume synchronization.

(psycopg2.IntegrityError) duplicate key value violates unique constraint “lead_idx_rpm_account_id__c”

This problem can have several different causes.

Sandbox Refresh

If you’ve refreshed a sandbox organization without destroying and recreating the Connect connection, you might get some of these errors. We strongly recommend creating a new connection when you reload a sandbox instead of trying to reuse the existing one.

Insert Round-Trip Issues

If the conflict is on an SFID field, such as "contact_idx_sfid", it might be due to a race condition related to inserting records into your database. When you insert a new record into your database and Connect pushes that record to Salesforce, Connect will wait to receive the success response from Salesforce and update the database record with the newly created row’s SFID. Connect will sometimes also get that row back as part of its regular polling while the initial insert is still in process. This results in a race condition where both processes are attempting to write a record with the same SFID. This can cause unique index conflicts, but it can also cause duplicate records in the database where one record is missing the SFID.

The workaround is to add an external ID to any object you’ll be creating from the database side, and make sure to populate each new record with a unique ID (such as a GUID) when you create it. Then, add a unique index on that external ID. That way, if Connect attempts to write a duplicate record, the unique index will cause the write to fail. You’ll still see index violations in your logs, but if it’s on the external ID field, which means a duplicate record was prevented.

If you add an external ID field to an object, it’s important not to change that ID once it’s set.

Unable to reload mapping with id: abcdef12…

If you’ve recently changed a mapping or imported a configuration, you may see this error. Check the status of the mapping in your Connect Dashboard. If you see BULK_LOADING, this means that Connect is in the middle of a bulk loading operation that can’t be interrupted. You’ll need to wait until the operation is complete to reload the mapping.

QUERY_TIMEOUT: Your query request was running for too long. Trying again later.;

This error usually results in multiple error messages that look something like this:

Batch 751m0000001AoAtAAK of job 750m0000001BfWOAA0 failed: InternalServerError : Retried more than 15 times; InvalidBatch : Failed to process query: QUERY_TIMEOUT: Your query request was running for too long. Trying again later.; InvalidBatch : Failed to process query: QUERY_TIMEOUT: Your query request was running for too long. Trying again later.; InvalidBatch : Failed to process query: QUERY_TIMEOUT: Your query request was running for too long. Trying again later.; (...)

This error comes directly from Salesforce. Connect uses the bulk API to load large amounts of data. Occasionally, a bulk query will time out, and Connect will automatically retry the query. If the query continues to time out after several retries, you’ll need to open a ticket with Salesforce to investigate why it’s happening.

Batch 54321000007DvJXYZ0 of job 54321000005lfIZXYZ failed: InvalidBatch : Failed to process query: INVALID_FIELD

This error typically indicates there has been some amount of schema drift between a mapping’s configuration and Salesforce. Most often a field has been removed or renamed in Salesforce, but that field remains in the mapping’s configuration. To correct the issue, update the mapping configuration removing the invalid field.

In other instances this error may indicate a permission issue, where a particular field is included in a mapping’s configuration, but is no longer visible to the Salesforce user on the connection. To resolve the issue, try re-authenticating with different Salesforce user credentials or modifying the permissions of the current user. Once the permission issue is corrected, you can either update the mapping configuration by removing the field(s) and then adding them back to force a field level resync, or you can reload the entire mapping.

The Salesforce configuration saved for this object no longer maps to the current Salesforce data model

If you make changes to mapped objects in Salesforce, such as changing the data type of a field, Heroku Connect will not automatically update your database schema. You may see errors such as this one as a result. To resolve the issue, edit the mapping in your Connect Dashboard.

“Server raised fault: ‘REQUEST_LIMIT_EXCEEDED: ConcurrentPerOrgApex Limit exceeded” or “System.LimitException: Apex CPU time limit exceeded”

When you write records into a table configured to send updates to Salesforce, Connect will periodically poll your database and group many records—up to 200—into a single request to the Salesforce API.

If your object has Apex code that gets triggered when new records are created, Salesforce imposes limits on the amount of computing resources it dedicates to those triggers. As a result, you may see one of the above errors if you insert more records than usual. This Salesforce guide describes some ways to optimize your Apex code to improve performance.

If this continues to happen, contact Heroku support about lowering your write batch size. We can limit your insert batches to 100 or 50 records, but this may also increase the latency of inserting new records.

“Expired transition aborted by health_check” or “Expired transition aborted by sweep”

Both of these messages appear in your logs when a sync worker dyno has hung. Every 15 minutes, we run a health check on your mappings from a different dyno, and if the health check notices a hung process, it will kill it and reset the state of the mapping so it starts polling again. This can happen for a variety of reasons, such as temporary network outages or dynos restarting.

query_wait_timeout: server closed the connection unexpectedly

This can happen if the database suddenly disconnects during a sync operation. Connect should recover automatically, but if it doesn’t, you can resume your connection from the Connect Dashboard.

Streaming error: 403::Organization total events daily limit exceeded

This error means that you’ve used up your available PushTopic events. Sync will continue, but it will fall back to the polling interval you’ve configured for each mapping. Events will resume automatically when the rolling 24-hour window resets.

function get_xmlbinary() does not exist

Connect creates a function called get_xmlbinary in the public schema of your database, which it uses as part of the sync process. If you remove the public schema from your search_path, Connect won’t be able to find that function, and sync will fail.

Too many polling errors. Polling will be disabled for up to 15 minute(s)

This error indicates that polling the database or Salesforce has resulted in consecutive and unexpected failures. As a result, Connect will back off polling for the specified duration to allow time for the underlying problem to be resolved. You can look for a notification at the top of your Connect Dashboard that might explain the problem, or go to the Logs tab and filter for Error log lines to investigate. These issues are often related to your database schema being out of date, which can happen if you change your Salesforce object fields without editing your Connect mapping to update it.

Too many bulk errors, bulk usage will be disabled for up to 2 hour(s)

This error indicates that bulk polling requests to Salesforce have resulted in consecutive and unexpected failures. As a result, Connect will back off bulk polling for the specified duration to allow time for the underlying problem to be resolved. You can look for a notification at the top of your Connect Dashboard that might explain the problem, or go to the Logs tab and filter for Error log lines to investigate. These issues are often related to exceeding bulk usage limits in Salesforce, which you should be able to see on your Connect Dashboard.

SERVER_UNAVAILABLE: Request timed out waiting for connection

You may see something similar to this message in your logs:

faultcode = "sf:SERVER_UNAVAILABLE" faultstring = "SERVER_UNAVAILABLE: Request timed out waiting for connection: [config 1,000ms, actual 1,001ms]" detail = (detail){ UnexpectedErrorFault = (UnexpectedErrorFault){ exceptionCode = "SERVER_UNAVAILABLE" exceptionMessage = "Request timed out waiting for connection: [config 1,000ms, actual 1,001ms]" } } }

This error happens when Salesforce has problems connecting to an internal database. It should be a transient issue that resolves itself in a few minutes. If it happens repeatedly, please contact Heroku support.

Server raised fault: 'OPERATION_TOO_LARGE: exceeded 100000 distinct who/what’s’

OPERATION_TOO_LARGE errors are the result of not granting the View All Data permission to your authenticated Salesforce user. Without this permission, Salesforce has to run additional queries to check if your user has permission to view each row. For larger mappings, those queries can result in OPERATION_TOO_LARGE errors. Unfortunately, the only way to fix this is to remove the need for permissions queries by granting View All Data for this object, and if necessary, related objects.

Parsing SOAP response failed: SAXParseException: <unknown>:1:0: syntax error

This error indicates that Heroku Connect made a SOAP request to Salesforce but the response received was not valid SOAP XML. This is a transient condition that may occur if Salesforce experiences an internal error. Heroku Connect will automatically retry the SOAP request.

SOAP transport error: BadStatusLine

This error indicates that the response from Salesforce was malformed. This error is transient in nature. As such, subsequent attempts to sync the record(s) which caused this error should succeed. This error does not represent any serious issues with your Connect mappings.

(psycopg2.OperationalError) FATAL: too many connections for role

This error occurs when Connect tries to open a connection to your database but you’ve already reached your connection limit. For very active connections, Connect may use 10 or more database connections. For this reason, we strongly advise against using hobby tier database plans with Connect.

CREATE TEMPORARY TABLE _tmp_sf…

You may see statements related to a temporary table appear in your log stream:

CREATE TEMPORARY TABLE _tmp_sf_contact AS (...)
CREATE UNIQUE INDEX ON
         _tmp_sf_contact (sfid)
CREATE INDEX ON
         _tmp_sf_contact (__operation, sfid)

These temporary tables are created by the Connect sync process in order to more efficiently sync inserts and updates from Salesforce to your database. They do not cause any performance impact to your database, and they are safe to ignore.

Value does not exist or does not match filter criteria

This error can happen if you attempt to insert an invalid value into a picklist field. Connect supports the picklist data type, but does not provide any data validation.

Missed Updates Due to Salesforce Transactions

It is possible that a small set of records may be locked in a transaction at the time of a poll and therefore not available to be synced. Heroku Connect handles this by performing a poll for Salesforce IDs that should have been included 2 minutes after successful poll completion. Any missed records will automatically be synced when detected. This “insurance” poll reconciles records in flight at time of last sync operation.

Errors with associated notifications

When errors occur that require user intervention, Heroku Connect sends notifications to all users that have chosen to receive them. To view a list of users that will receive notifications, navigate to the Settings tab, Manage Connection in the dashboard: the Access section lists users who have access to the Connect dashboard and is where the Notifications Enabled setting can be configured.

You will receive notifications for the errors summarized below. The notification message describes the error that has occurred and includes helpful information so that you can understand and resolve the problem. You will also receive notifications when an error that occurred previously has been resolved.

Bad configuration

A bad configuration error can occur when changes to the Salesforce object or Heroku Postgres table used by a mapping are changed. The mapping will not be synchronized until the error is resolved however other mappings should continue to synchronize as normal.

Change user permissions

This error occurs when the user credentials you use to authenticate to Salesforce don’t have the correct permissions to allow Heroku Connect to efficiently synchronize a large number of records. Re-authenticating with different Salesforce user credentials or modifying the permissions of the current user will resolve the error.

Connection error

A connection error can occur for a number of reasons and may prevent synchronization from occurring on one or more of your mappings. You will be asked to check the logs in the Heroku Connect dashboard in order to identify the exact nature of the error.

Database unavailable

If the Heroku Postgres database cannot be reached then Heroku Connect will be unable to synchronize any mappings. You will need to review your database configuration in order to resolve this problem.

Reauthorization required

If the user credentials used to authorize Heroku Connect with Salesforce expire or change then synchronization will stop for all mappings and you will need to reauthorize with Salesforce in order for it to resume.

Salesforce Bulk Load Error

This error occurs when there was a problem during the initial bulk load or reload of a mapping. You can investigate the cause of the error in the Heroku Connect dashboard by viewing the Logs tab and filtering for Error log lines. In most cases these errors are due to bulk batch failures. A failure during a bulk load operation can leave a mapping in an inconsistent state, and cannot be automatically recovered from. After identifying and correcting the cause of the error, the mapping should be reloaded.

Answers to the most frequently asked questions are available in the Heroku Connect FAQ article.

Feedback

Log in to submit feedback.