Action States

Call a server-side controller action from a client-side controller. The action can have different states during processing.

The possible action states are:

NEW: The action was created but is not in progress yet

RUNNING: The action is in progress

SUCCESS: The action executed successfully

ERROR: The server returned an error

INCOMPLETE: The server didn’t return a response. The server might be down or the client might be offline. The framework guarantees that an action’s callback is always invoked as long as the component is valid. If the socket to the server is never successfully opened, or closes abruptly, or any other network error occurs, the XHR resolves and the callback is invoked with state equal to INCOMPLETE.

ABORTED: The action was aborted. This action state is deprecated. A callback for an aborted action is executed only if you explicitly add a handler for it.

See Also

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
Apex Server-Side Controller Overview
AuraEnabled Annotation
Creating an Apex Server-Side Controller
Using Apex to Work with Salesforce Records
Granting User Access for Apex Classes
Securing Data in Apex Controllers
Calling a Server-Side Action
Passing Data to an Apex Controller
Returning Data from an Apex Server-Side Controller
Returning Errors from an Apex Server-Side Controller
Action States
Queuing of Server-Side Actions
Storable Actions
Abortable Actions
Action Limits and Considerations
Testing Your Apex Code
Making API Calls from Apex
Make Long-Running Callouts with Continuations
Creating Components in Apex
Testing Components
Debugging
Performance
Reference
Previous PDF Versions