Error 'Too many queueable jobs' in the Salesforce CPQ Package

This error is most commonly seen as a result of custom automation designed to work in conjunction with the Salesforce CPQ package. This is a result of an Apex Limitation related to when a single transaction kicks off more than one queued job in an org.

If you encounter this error, analyze automation records that make updates to any of the following objects as these have the potential to en-queue a job:

• Opportunity
• Order
• Contract
• Order Product
• Subscription
• Contract Line Item
• Quote
• Quote Line
• Quote Line Group

Actions that can queue asynchronous jobs in the Salesforce CPQ Package

• Setting Contracted to TRUE on an Order (Only if Contract in Foreground = FALSE in the CPQ installed package settings, otherwise Contract creation is synchronous)
• Updating any field on a Quote Line record from outside of the Line Editor (via Apex or via the record detail page)
• Updating a field that is a part of the Calculating Fields field set on the Quote object (via Apex or via the record detail page)
• Setting Renewal Forecast to TRUE on a contract
• Setting Renewal Quoted to TRUE on a contract
• Adding/Editing a Subscription Record if its associated Contract has Renewal Forecast set to TRUE and no Quotes have been generated on the Renewal Opportunity
• Clicking the Create Order button on a Quote when Allow Multiple Orders is set to FALSE in package settings if the order contains usage products
• Clicking the Create Order button on a Quote and selecting at least one product for the Order when Allow Multiple Orders is set to TRUE in package settings if choosing usage products for the order
• Setting the Ordered field to TRUE on a Quote if quote contains a usage product
• Setting the Ordered field to TRUE on an Opportunity if the primary quote contains a usage product
• Preview Document
• Generate Document

A general rule of thumb is that any callouts to the Heroku service will en-queue a job (both the calculation and document services). It's important to note that generating an order and renewing contracts are both processes which run calculations.

When encountering this error, analyze automation added to the org to see what updates are being made to the objects mentioned above and whether the customization in the org would cause multiple entries from the list to be executed (or some entries to be executed more than once). In many instances, moving immediate actions from workflow rules, flows, and process builders to time delayed actions can prevent the errors as the second queued job will be enqueued from the new time-delayed action.

NOTE: For additional information, read our help article General Tips to Troubleshoot Apex Governor Limit Errors in CPQ.