Skip to main content
Conga Support

Conga Workflow Caveats and Warnings

Conga Workflow is limited to 500 transactions per 24-hour period. Conga Workflow is a transaction-based service. You will be charged per transaction (a.k.a service event).

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

If you’re updating records with a tool like the Salesforce Data Loader, we strongly recommend you use the credentials of a user whose Profile has the “Send Outbound Messages” permission disabled to avoid inadvertently triggering mass execution of Conga Workflow.

Keep in mind that the number of outbound emails permitted through Salesforce is dependent on your Salesforce edition. Consider using Conga Composer’s integration with SendGrid if you need to exceed the Salesforce email limits.

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

Since an Outbound Message operates under the authority of a named user, be careful to ensure that you do not trigger a merge operation that exposes more information than a user would normally have privilege to access. Consider using a collection of workflow rules and outbound messages that execute depending on the identity of the end-user.

When using Conga products and DocuSign in a fully automated fashion (such as using the background parameter/value pair &DS7=17, Conga Workflow, or Conga Conductor) 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.

User fields normally made available when executing a standard Conga Composer solution will, in the case of a Conga Workflow-triggered operation, reflect the values represented by the user under whose authority the workflow solution is running (the User to Send As on the outbound message). Thus, an invoice template with a merge field intended to retrieve the name of the person clicking a Conga Composer button/link will instead populate with the name of the user defined as the User to Send As on the Outbound Message.

Ensure that ampersands (&) in text fields passed via Conga Workflow have a space before and after the ampersand character. For more information, see Replace Ampersands (&) in Reference Field Data.

Conga Workflow is intended to be executed against individual records. While it is possible to update many records in Salesforce, resulting in a batch of Conga Workflow requests, the use of Conga Workflow in this manner risks tripping an automatic Conga system governor designed to prevent a “runaway” process from “looping” uncontrollably and potentially harming certain systems.