
31
MarTo keep automated renewals and the amendment process running smoothly, it's worth building some light-touch monitoring into your workflow. One effective way to do this is by leveraging the SBQQ__RecordJob__c object, which is created when a record initiates an Apex Job.
This object captures job status, error details, and links to the related records—making it easier to spot background issues before they cause downstream delays. To identify records that may need attention—such as failed background jobs related to renewal or amendment processing—this SOQL query is a great starting point:
SELECT Id, CreatedDate, SystemModStamp, SBQQ__RecordId__c, SBQQ__JobStatus__c, SBQQ__JobDetails__c
FROM SBQQ__RecordJob__c
WHERE SBQQ__JobStatus__c = 'Failed'
ORDER BY SystemModStamp DESC
You can also create a report on this object and subscribe to it via email. While it won’t give you real-time alerts, it’s a scalable way to keep an eye on silent failures without needing to manually check individual records.
It’s also worth checking for queued jobs. Jobs stuck in a queued state can occasionally block further processing. Deleting these when can often help restart downstream activity. This query helps surface those so they can be reviewed and cleared as needed:
SELECT Id, CreatedDate, SBQQ__RecordId__c, SBQQ__JobStatus__c, SBQQ__JobDetails__c
FROM SBQQ__RecordJob__c
WHERE SBQQ__JobStatus__c = 'Queued'
ORDER BY CreatedDate DESC
Putting this kind of monitoring in place gives your team better visibility, faster troubleshooting, and a more stable contracting experience. At Milo Massimo, this is one of the areas we routinely keep an eye on when supporting clients behind the scenes—and something we often recommend building into day-to-day ops.
Comments (0)