Monitor Transactions

List<AsyncApexJob> paymentJobs = [
    SELECT Id, Status, NumberOfErrors, CompletedDate
    FROM AsyncApexJob
    WHERE ApexClass.Name = 'ProcessPaymentJob'
    ORDER BY CreatedDate DESC
    LIMIT 20
];

for (AsyncApexJob job : paymentJobs) {
    System.debug(job.Status + ' - Errors: ' + job.NumberOfErrors);
}

This is Module 38's AsyncApexJob monitoring lesson, filtered specifically to ProcessPaymentJob — a support team could run this (or a scheduled report built on it) to confirm payment jobs are actually completing, not silently stuck.

List<Order__c> stuckOrders = [
    SELECT Id, Status__c, LastModifiedDate
    FROM Order__c
    WHERE Status__c = 'Ready for Payment' AND LastModifiedDate < :DateTime.now().addMinutes(-10)
];

An Order__c still sitting at 'Ready for Payment' more than 10 minutes after being set there suggests something went wrong — the trigger might not have fired, the Queueable job might have failed silently, or an unexpected exception occurred somewhere in the chain. This query surfaces exactly that gap for investigation.

Module 26's revenue rollup or Module 27's leave requests being briefly out of sync is inconvenient; a payment that's silently stuck — neither charged nor clearly failed — is a genuinely serious problem for both the business and the customer. Financial processes specifically deserve active monitoring, not just correct code, because the cost of an unnoticed failure is meaningfully higher.