System Events

The framework fires several system events during its lifecycle.

You can handle these events in your Lightning apps or components, and within Salesforce1.

Event Name Description
aura:doneRendering Indicates that the initial rendering of the root application has completed. We don't recommend using the legacy aura:doneRendering event except as a last resort. Unless your component is running in complete isolation in a standalone app and not included in complex apps, such as Lightning Experience or Salesforce1, you probably don’t want to handle this application event. The container app may trigger your event handler multiple times.
aura:doneWaiting Indicates that the app is done waiting for a response to a server request. This event is preceded by an aura:waiting event. We don't recommend using the legacy aura:doneWaiting event except as a last resort. The aura:doneWaiting application event is fired for every server response, even for responses from other components in your app. Unless your component is running in complete isolation in a standalone app and not included in Lightning Experience or Salesforce1, you probably don’t want to handle this application event. The container app may fire server-side actions and trigger your event handler multiple times.
aura:locationChange Indicates that the hash part of the URL has changed.
aura:noAccess Indicates that a requested resource is not accessible due to security constraints on that resource.
aura:systemError Indicates that an error has occurred.
aura:valueChange Indicates that an attribute value has changed.
aura:valueDestroy Indicates that a component has been destroyed.
aura:valueInit Indicates that an app or component has been initialized.
aura:valueRender Indicates that an app or component has been rendered or rerendered.
aura:waiting Indicates that the app is waiting for a response to a server request. We don't recommend using the legacy aura:waiting event except as a last resort. The aura:waiting application event is fired for every server request, even for requests from other components in your app. Unless your component is running in complete isolation in a standalone app and not included in Lightning Experience or Salesforce1, you probably don’t want to handle this application event. The container app may fire server-side actions and trigger your event handler multiple times.