---
schema_version: "1"
id: de86bcb3ac4382fc78c02a9eff2c30c15f0630132979f92ea48b520fe39acc50
title: System Events
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/aura-platform/guides/aura/events/events-system.md
canonical_url: https://developer.salesforce.com/docs/platform/aura-platform/guide/events-system.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 33340fa40237c42a25483951edcee23adfbd41dfdaa8c846f2d6235d797eeb19
products:
  - Lightning Aura Components Developer Guide
  - Platform Developer Content
---

# System Events

The framework fires several system events during its lifecycle.

You can handle these events in your Lightning apps or components, and within the Salesforce mobile app.

For examples, see the [Lightning Component Library](https://developer.salesforce.com/docs/platform/aura-platform/components/component-library.md).

|**Event Name**|**Description**|
|--------------|---------------|
|`aura:doneRendering` (deprecated)|Indicates that the initial rendering of the root application has completed.|
|`aura:doneWaiting` (deprecated)|Indicates that the app is done waiting for a response to a server request. This event is preceded by an `aura:waiting` event.|
|`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` (deprecated)|Indicates that the app is waiting for a response to a server request.|

**Note:** The `aura:doneRendering` event is deprecated. Unless your component is running in complete isolation in a standalone app and not included in complex apps, such as Lightning Experience or the Salesforce mobile app, the container app may trigger your event handler multiple times. This behavior makes it difficult to handle each event appropriately.

**Note:** The `aura:doneWaiting` event is deprecated. 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 the Salesforce mobile app, the container app may trigger your event handler multiple times. This behavior makes it difficult to handle each event appropriately.

**Note:** The `aura:waiting` event is deprecated. 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 the Salesforce mobile app, the container app may trigger your event handler multiple times. This behavior makes it difficult to handle each event appropriately.