Lightning Components Developer Guide

What is the Lightning Component Framework?
Quick Start
Creating Components
Using Components
Communicating with Events
Creating Apps
App Overview
Designing App UI
Creating App Templates
Content Security Policy Overview
Styling Apps
Using JavaScript
JavaScript Cookbook
Using Apex
Creating Server-Side Logic with Controllers
Apex Server-Side Controller Overview
Creating an Apex Server-Side Controller
Returning Errors from an Apex Server-Side Controller
Calling a Server-Side Action
Queueing of Server-Side Actions
Abortable Actions
Storable Actions
Creating Components
Working with Salesforce Records
Testing Your Apex Code
Making API Calls from Apex
Controlling Access
Using Object-Oriented Development
Caching with Storage Service
Using the AppCache
Distributing Applications and Components
Debugging
Reference
PDF

Newer Version Available

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

Queueing of Server-Side Actions

The framework queues up actions before sending them to the server. This mechanism is largely transparent to you when you're writing code but it enables the framework to minimize network traffic by batching multiple actions into one request.

Event processing can generate a tree of events if an event handler fires more events. The framework processes the event tree and adds every action that needs to be executed on the server to a queue.

When the tree of events and all the client-side actions are processed, the framework batches actions from the queue into a message before sending it to the server. A message is essentially a wrapper around a list of actions.

If your action is not executing, make sure that you're not executing code outside the framework's normal rerendering lifecycle. For example, if you use window.setTimeout() in an event handler to execute some logic after a time delay, wrap your code in $A.getCallback().

Tip