Caveats and Warnings for Conga Batch

Conga Batch is limited to 50 records per batch for consolidated output or when launching from a Salesforce List View button. Up to 1000 records may be included in the batch for distributed output.

Each Master Object record in the batch will use one service event. Service events are deducted from your annual subscription plan of service events.

Each Conga Batch merge operation consumes API requests; the number varies depending on the nature and complexity of the solution as well as how many records are in the batch. Therefore, you’ll need to gauge the number of Conga Batch operations that will take place in your instance with the number of API requests you’re allowed in a 24-hour period.

While not generally necessary, set a 12-hour session timeout value when using Conga Trigger or a Scheduled Conga Batch to increase the likelihood that a session is still active when the document processing takes place.

If you have a Conga Batch scheduled that utilizes reports, remain in Classic. If you switch to Lightning, a scheduled Conga Batch will pick this up and not be able to generate data for that report as Conga cannot read report data in Lightining.

When using Conga products and DocuSign in a fully automated fashion (such as using the background parameter/value pair &DS7=17, Conga Trigger, or Conga Batch) the DocuSign Username and Salesforce User Email must match. If not, you will receive this error: Error: CreateEnvelope in DocuSignAPI. The UserID does not have a valid membership in this Account.