Lightning Aura Components Developer Guide

Introducing Aura Components
Quick Start
Creating Components
Using Components
Communicating with Events
Communicating Across the DOM with Lightning Message Service
Creating Apps
Styling Apps
Developing Secure Code
Using JavaScript
Working with Salesforce Data
Lightning Data Service
Using Apex
Creating Server-Side Logic with Controllers
Testing Your Apex Code
Making API Calls from Apex
Make Long-Running Callouts with Continuations
Work with a Continuation in an Apex Class
@AuraEnabled Annotations for Continuations
Aura Component Continuations Example
Continuation-Specific Limits
Creating Components in Apex
Testing Components
Debugging
Performance
Reference
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Continuation-Specific Limits

Because continuations can lead to multiple long-running actions, there are some limits on their usage.

The limits for using continuations in Apex are listed in the Apex Reference Guide.

Here are a few more limits specific to usage in Aura components.

Up to three callouts per continuation
A single Continuation object can contain a maximum of three callouts.
Serial processing for continuation actions
The framework processes actions containing a continuation serially from the client. The previous continuation action call must have completed before the next continuation action call is made. At any time, you can have only one continuation in progress on the client.
DML operation restrictions
An Apex method that returns a Continuation object can’t perform Data Manipulation Language (DML) operations. DML statements insert, update, merge, delete, and restore data in Salesforce. If a DML operation is performed within the continuation method, the continuation execution doesn’t proceed, the transaction is rolled back, and an error is returned.
You can perform DML operations in the Apex callback method for the continuation.