CPQ error 'Could not calculate quote prices. This quote is now in an invalid state. Recalculate your quote to render it'

If you are seeing this generic error message at the top of a Quote record in your org, it means that an asynchronous calculation job for that Quote has failed. To troubleshoot this error message, you can do one of the following things:

1. Attempt to recalculate the Quote by making an edit to the quote outside of the line editor to one of the fields in the Calculating Fields field set on the Quote object - If you remain on the Quote record detail page during the recalculation until completion, any error message from the Apex Job created from the recalculation shows up in its raw format (not obscured by this generic error message).
2. Find the Record Job associated with the quote - The ID of the Quote appears in the text for the SBQQ__RecordId__c field on the Record Job. The SBQQ__JobId__c field contains the ID of the Apex Job associated with the Record Job.
   1. You can review your Apex Job error message by first finding the Apex Job ID via this query:
      1. SELECT SBQQ__JobId__c FROM SBQQ__RecordJob__c WHERE SBQQ__RecordId__c LIKE '%<Your Quote ID>%'
         1. Replace <Your Quote ID> with the quote record's ID, but keep the single quotes and the percent signs when you make the replacement (e.g. '%a0l61000007ieMY%'). The return value in the SBQQ__JobId__c field can be used in a second query to get your failure message.
   2. This ExtendedStatus field return contains the failure message from the Apex Job associated with the failed Quote Calculation. Use the query below to view the extended status:
      1. SELECT ExtendedStatus FROM AsyncApexJob WHERE Id = '<SBQQ__JobId__c from first query>'
3. Attempt to run your calculation from the Quote Line Editor - This does not behave exactly the same as the asynchronous calculations. Quote Line Editor calculations are carried out in Javascript as opposed to Asynchronous Calculations that are sent to the Heroku service for calculation. However, many of the same error messages appear during both asynchronous and synchronous calculations. It can be worth trying to get error information and quickly run tests of changes.