Apex Developer Guide

Apex Developer Guide
Release Notes
Getting Started with Apex
Writing Apex
Running Apex
Invoking Apex
Anonymous Blocks
Triggers
Asynchronous Apex
Queueable Apex
Detecting Duplicate Queueable Jobs
Transaction Finalizers
Transaction Finalizers Error Messages
Apex Scheduler
Batch Apex
Future Methods
Large Data Processing with Cursors and Queueable Apex Versus Batch Apex
Exposing Apex Methods as SOAP Web Services
Exposing Apex Classes as REST Web Services
Apex Email Service
Using the InboundEmail Object
Visualforce Classes
JavaScript Remoting
Apex in AJAX
Apex Transactions and Governor Limits
Using Salesforce Features with Apex
Integration and Apex Utilities
Debugging, Testing, and Deploying Apex
Apex Reference
Appendices
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Transaction Finalizers Error Messages

Troubleshoot both semantic and run-time issues by analyzing these error messages.
This table provides information about error messages in your Apex debug log.
Table 1. Troubleshooting Errors in Apex Debug Log
Error Message Failed Context Reason for Failure
More than one Finalizer cannot be attached to same Async Apex Job Queueable Execution System.attachFinalizer() is invoked more than once in the same Queueable instance.
Class {0} must implement the Finalizer interface Queueable Execution The instantiated class parameter to System.attachFinalizer() doesn’t implement the System.Finalizer interface.
System.attachFinalizer(Finalizer) is not allowed in this context Non-Queueable Execution System.attachFinalizer() is invoked in an Apex context that's not executing a Queueable instance.
Invalid number of parameters Queueable Execution Invalid number of parameters to System.attachFinalizer()
Argument cannot be null Queueable Execution System.attachFinalizer() is invoked with a null parameter.
If you have a Splunk Add-On for Salesforce, you can analyze error messages in your Splunk log. This table provides information about error messages in the Splunk log.
Table 2. Troubleshooting Errors in Splunk Log
Error Message Reason for Failure
Error processing finalizer for queueable job id: {0} Runtime error while executing Finalizer. This error can be an unhandled catchable exception or uncatchable exception (such as a LimitException), or, less commonly, an internal system error.
Error processing the finalizer (class name: {0}) for the queueable job id: {1} (queueable class id: {2}) Runtime error while executing Finalizer. This error can be an unhandled catchable exception or uncatchable exception (such as a LimitException), or, less commonly, an internal system error.