Contents
What happens to the ID of a queueable apex job?
The ID of a queueable Apex job isn’t returned in test context— System.enqueueJob returns null in a running test. To run a job after some other processing is done first by another job, you can chain queueable jobs. To chain a job to another job, submit the second job from the execute () method of your queueable class.
What kind of processes can be run in apex?
Apex processes that run for a long time, such as extensive database operations or external web service callouts, can be run asynchronously by implementing the Queueable interface and adding a job to the Apex job queue.
How to take control of your asynchronous apex processes?
Take control of your asynchronous Apex processes by using the Queueable interface. This interface enables you to add jobs to the queue and monitor them. Using the interface is an enhanced way of running your asynchronous Apex code compared to using future methods.
How to test the execution of a queueable job?
This example shows how to test the execution of a queueable job in a test method. A queueable job is an asynchronous process. To ensure that this process runs within the test method, the job is submitted to the queue between the Test.startTest and Test.stopTest block.
How are non primitive types used in queueable apex?
Using non-primitive types: Your queueable class can contain member variables of non-primitive data types, such as sObjects or custom Apex types. Those objects can be accessed when the job executes. Chaining jobs: You can chain one job to another job by starting a second job from a running job.
What’s the maximum stack depth for queueable apex?
For Developer Edition and Trial organizations, the maximum stack depth for chained jobs is 5, which means that you can chain jobs four times and the maximum number of jobs in the chain is 5, including the initial parent queueable job. When chaining jobs with System.enqueueJob, you can add only one job from an executing job.
How does transaction finalizers work in queueable apex?
The Transaction Finalizers feature enables you to attach actions, using the System.Finalizer interface, to asynchronous Apex jobs that use the Queueable framework. A specific use case is to design recovery actions when a Queueable job fails.
How to check how many queueable jobs have been added in one transaction?
To check how many queueable jobs have been added in one transaction, call Limits.getQueueableJobs (). Because no limit is enforced on the depth of chained jobs, you can chain one job to another. You can repeat this process with each new child job to link it to a new child job.
The Transaction Finalizers feature enables you to attach actions, using the System.Finalizer interface, to asynchronous Apex jobs that use the Queueable framework. A specific use case is to design recovery actions when a Queueable job fails. Troubleshoot both semantic and run-time issues by analyzing these error messages.
When to use queueable instead of future methods?
Chaining jobs: You can chain one job to another job by starting a second job from a running job. Chaining jobs is useful if you need to do some sequential processing. Because queueable methods are functionally equivalent to future methods, most of the time you’ll probably want to use queueable instead of future methods.