Outreach CRM Poller Functionality

Created by Aye Myat, Modified on Fri, 13 Mar at 6:39 PM by Aye Myat

Objective

This article provides information on CRM integration poller functionality to assist users in troubleshooting and investigating CRM sync issues.

Applies To

CRM integration
Poller

What records are included in the CRM poller sync?

Any record created or updated in the CRM since the last poll. This includes records that have been detected but not synced by previous polls. This excludes records that do not meet polling conditions.

How does the CRM poller determine what timeframe to sync records from?

Salesforce

The start time for the next poll is based on the Salesforce Last Date Covered (LDC) value. If LDC has been static for 30 minutes or more the start time for the next poll will be based on the timestamp of the last record processed in the current poll.

Dynamics

The start time for the next poll is based on the timestamp of the last record processed in the current poll.

How many records can the CRM poller sync per API call?

Between 0 and 2000. The number of records synced per API is based on the total bytes size of the data being synced.

For example, Salesforce has a 16,384 bytes limit. The total bytes size is influenced by the number of fields included in the request (CRM integration field mappings) and the field types (e.g. long text area). You can read more in the Salesforce documentation here and here.

How many records can the CRM poller sync per polling period?

Between 0 and 50,000. The number of records synced per polling period is based on the batch size (records synced per API call) and total number of API calls used (maximum 25 per polling period).