i'm trying to understand the Genesys Cloud Contact List Sync Job
Important: Due to Salesforce and Genesys Cloud limits, we recommend only syncing 1,000 campaign members in total for each sync job. Higher numbers might work but not in all cases. For more information, see Campaign members are not syncing to Genesys Cloud.
what happen if we have campaign has 5000 members/contacts, if we choose
Campaign Member Count for Each Genesys Cloud API Request=500
Request Count for Each Job=2
is that only the first 1000 contact synced, then rest 4000 contacts will never be dialled ?
the maximum value we can set
Campaign Member Count for Each Genesys Cloud API Request=1000
Request Count for Each Job=5
if we have campaign with 6000 members, only first 5000 is synced, the rest 1000 will never be dialled, is that right ?
First of all, the contact list sync job setting affects only throughput (the rate at which campaign members are synced to Genesys Cloud). The integration will attempt to process all contacts eventually no matter what options you choose.
Campaign members are synced to contact lists in Genesys Cloud using a sequence of processing (sync) jobs in Salesforce. If there are too many campaign members to process in a single sync job, the integration will queue additional jobs in Salesforce, sequentially, in order to eventually sync all of the contacts. Each processing job sends some contact list data to Genesys Cloud through Genesys Cloud platform API requests.
You can change throughput by changing the number of campaign members to include in each request and the number of requests to send in each job. If you hit limits enforced by Salesforce or Genesys Cloud, then lower the Campaign Member Count or the Request Count.
I hope that clarifies things for the contact list sync job setting.