'Apex Governor Limit' errors seen in Salesforce CPQ

If a transaction fails with an Apex Governor Limit error message that points to the SBQQ namespace, the cause of the error is not necessarily within the CPQ package.

Admins should analyze custom records and fields that interact with the CPQ package. Special attention should be given to the automation and customization within the org.

The processes in the Salesforce CPQ namespace are not all designed to run multiple times in a single transaction. Custom code, Flows, or Process Builders are some of the items that may cause the managed package triggers to run multiple times, which can result in limit errors.
 

Suggestions to narrow down cause of error

• Turn off custom Triggers, Workflow Rules, Process Builders, and Flows on the following objects:
  • Quote
  • Quote Line
  • Quote Line Group
  • Opportunity
  • Opportunity Product
  • Order
  • Order Product
  • Contracts
  • Subscription
  • Asset
  • Subscribed Asset
  • Service Contract
  • Entitlement
  • Contract Line Item
  • Account
• Reduce the number of custom fields on the objects listed above.
• De-Activate all Product Rules and Price Rules in the org.
• Reduce the Amount of Quote Lines/Subscriptions/Contract Line Items/Order Line Items of the Quote/Contract/Service Contract/Order causing the errors.
• Reduce the number of Features, Product Options, and Configuration Attributes in bundles causing the errors on the quote.
• If a timeout error occurs during contracting, verify that your Org doesn't use 'Contracting in Foreground' (CPQ package settings), since having this feature enabled increases the risk of timeout.